7 ms·

So it begins: Why io.js instead of node.js? The latest versions of jsdom only work with io.js

• _pmf_ 11y ago
  Did you really expect a JS related framework to last more that 2 years?
  • sehr 11y ago
    jsdom isn't a framework
• gfodor 11y ago
  Have you tried jsdom-node? Its a node-compatible fork of jsdom. Be warned though that jsdom in general is deprecated, everyone is using dom.js now. (However it requires ES6.) (kidding)
  • modnine 11y ago
    I had not seen node-jsdom. I see that it is forked from jsdom 3.x, which still works with node.js. Do windows users mind having to install the visual c++ compiler?
    • MildlySerious 11y ago
      As a windows user, I avoid developing with node on windows machines, because building dependencies caused me trouble many times. pg, socket.io, bcrypt, jsdom, countless others. If it's just the vc++ compiler, chances are node devs already have it installed anyway if they do in fact work on a windows machine.
      • gfodor 11y ago
        Ok, this is just unbelievable. My original post was a complete fiction. I just made it up. 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. I thought these two replies about the C++ compiler were just continuing the joke. Honestly. 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. What. The. Fuck. https://www.npmjs.com/package/node-jsdom https://www.npmjs.com/package/node-jsdom
• arianvanp 11y ago
  I actually don't mind javascript moving so 'fast'. But heck I'm not a professional developer but just a student who likes to play with cool stuff.