danmactough/node-htmlencode

Wrapped version of http://www.strictly-software.com/htmlencode

node-htmlencode

A wrapped version of http://www.strictly-software.com/htmlencode library -- only two changes to the original:

1. Renamed global Encoder object to module.exports so it can be used as a Node module.
2. Fixed leaking global variable arr in htmlDecode method

Usage

In addition to the very minor changes described above, the library is wrapped in a function to allow you to require just the individual method(s) you want.

var htmlencode = require('htmlencode');
htmlencode.htmlEncode('<h1>Welcome</h1>');
// &lt;h1&gt;Welcome&lt;/h1&gt;

works the same as

var htmlEncode = require('htmlencode').htmlEncode;
htmlEncode('<h1>Welcome</h1>');
// &lt;h1&gt;Welcome&lt;/h1&gt;

If you want to change to using numeric HTML entities, you'll still want to do something like this:

var htmlencode = require('htmlencode');
htmlencode.EncodeType = 'numerical'; // Don't blame me. I didn't name it.
htmlencode.htmlEncode('<h1>Welcome</h1>');
// &#60;h1&#62;Welcome&#60;/h1&#62;

Also provided is module.exports.Encoder, the wrapper class, so you can do something like this if you so choose:

var htmlencode = require('htmlencode');
var widget = new htmlencode.Encoder('numerical');
widget.htmlEncode('<h1>Welcome</h1>');
// &#60;h1&#62;Welcome&#60;/h1&#62;

node-htmlencode's Issues

Whitespaces are not encoded correctly

When a string consists only of whitespaces htmlEncode(" ") returns just an empty string with lenght = 0.

decode problem

When I encode the source and decode it, one of the base64 signatures is corrupted.

test2.txt

npm publish 0.0.4

You still can't see repo in npmjs.org. Can you npm publish please?

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.