incompatibility with Node.js as of version 4x

Note that as of our 4.0.0 release, jsdom no longer works with Node.js™, and instead requires io.js. You are still welcome to install a release in the 3.x series if you are stuck on legacy technology like Node.js™.

To be perfectly frank, to release this version in the wild, and to publish it on npmjs.com - the de facto source of information about community-contributed packages for Node - is grossly irresponsible in light of the incompatibility with Node.js

Those of us who use Gulp as a build system, and thus, rely on Node modules, which may in turn, rely on other Node modules, including this one, are now faced with a fatal error upon running npm install and attempting to use Gulp.

[kris-o3]

a helpful hint following your quite-severe advisory to suggest adding:

"jsdom": "3.1.2"

to the devDependencies of package.json at the root level of a Gulp build configuration, or similar, would be surely more helpful than the advisory alone… strongly recommend doing this, lest more suffer the time i wasted, needlessly.

[kris-o3]

how to easily do that isn’t exactly obvious… in my case, it was gulp-packer that was dependent upon it and now giving a fatal error. i thought i would now have to edit its package.json every time it is reinstalled. however, adding:

"jsdom": "3.1.2"

to devDependencies in the same package.json used by Gulp does resolve this issue.