So what does it mean now that node.js and io.js have kissed and made up?

[Tom Fennelly]

Hi guys.

jsdom is a great tool. Only issue for us atm is that we are using node.js (so were abandoned by jsdom at v4) but would like to use a version of jsdom that doesn't depend on contextify (we have some windows users) and, from what I can see, the most recent version of jsdom doesn't (right?).

We are using a maven build tool called frontend-maven-plugin. It supports node and, given the fact that everyone are friends again, they rightly prefer not to make changes to support io.js until they can see what's happening.

What's the plan for jsdom?

Regards,

Tom.

[Domenic Denicola]

Once io.js is renamed to node.js, then indeed, node.js will be supported. The current thinking is that that will likely happen sometime in late August, with io.js/node.js 4.0.0. In the meantime, you can use io.js/node.js 3.x and get all the benefits of jsdom.

--
You received this message because you are subscribed to the Google Groups "jsdom" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jsdom+un...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tom Fennelly]

Thanks for the prompt reply.

So is there a doc/mail on why jsdom 4+ is not currently support on node? I assume there's a technical reason?

[Domenic Denicola]

Yes. Node does not support the revised vm module that is used to replace contextify. It has a very hacky version that necessitated building contextify in the first place.

 

Node additionally does not support the many ES2015 features we are now using, including block scoping, classes, and template strings.

[Tom Fennelly]

Thanks for the insight.

[Godmar Back]

So does the revised io.js VM module support contextify-functionality on Windows?

--

[Domenic Denicola]

Yes. See https://github.com/tmpvar/jsdom/blob/master/Changelog.md#400