jsdom

It also supports node.js/io.js for node tests, as well as for front-end tests with something like jsdom.

Imagine my shock to realize that the fake jsdom-node project I made up actually exists (in the form of node-jsdom) and actually exists for the reason I made up.

Also great for jsdom (one of node's best features) soon running on node again!

Be warned though that jsdom in general is deprecated, everyone is using dom.js now.

Basically an old 1.x version of Jasmine, bolted to a test runner, a JSDom environment, and a ton of mostly working automocking magic.

Do yourself a favor and write React and test your components without a browser driver in good ol' JS with the occasional JSDom shim.

I can't speak on the performance difference between libxml and cheerio, but jsdom seems to be way slower than cheerio.

He already uses libxml, so cheerio or jsdom would be alternatives.

I see that it is forked from jsdom 3.x, which still works with node.js.

Finally, regarding testing, with React I've finally been able to consistently apply easy command-line unit testing to DOM code without worrying about setting up PhantomJS or JSDom and struggling to get initial tests working.

I made up jsdom-node, I made up the fact that it was a node.js compatible fork, I made up dom.js, I made it all up as satire to poke fun at the javascript community.

The readme says "Lightweight: no dependencies like jQuery, cheerio, or jsdom", I think the context is relevant for performance and/or size reasons.