Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Use jsdom rather than node-jsdom
See original GitHub issueI noticed that the tools depend on node-jsdom not jsdom and I’m guessing that the reason was because jsdom chased io.js. Given that they have converged I don’t see any need for node-jsdom to be used and that the original can be swapped back in.
In my (simple) testing it seems to work just fine, although I haven’t tried from the WebIDE, only the cli tools.
The reason that I’d like to see it switch back to just jsdom is that node-jsdom depends on contextify which is a real pain to get working smoothly on Windows, but has now been merged into node.js core so isn’t required.
Issue Analytics
- State:
- Created 8 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Actually I just managed to rip out jquery and jsdom. Not actually too painful: https://github.com/espruino/EspruinoTools/commit/f2ae108e4e1193ddab5878e5229dd7d156f29a84
I’ll update my project to give this a crack 😀