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.
Enhancement: Support .mjs & .cjs extensions
See original GitHub issueSupersedes #50 & #59 - Please see them for additional context
We currently have support for ESModules using the .esm.js extension and the esm module to transpile them on the fly. However, node 13 (and the upcoming 14) support the .mjs and .cjs extensions. I’ve run into a bunch of troubles reviewing, interpreting, and testing those features, but I’d like to support them.
I’d love some help here @ulrichb @cedx or anyone else with experience.
One other note: I believe this will be a breaking change because it seems the .cjs extension can’t be used outside a .mjs instance.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:5
- Comments:27 (10 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
@phated I had a go. It’s still WIP, but I could already use some feedback. BTW, it seems I found a way to keep things backwards-compatible all the way back to Node.js 0.10.
@yannbf That attempt still relies on a transpiler (in this case babel) to work. We can already do that using the esm package. What this issue is about, however, is leveraging Node’s native support for esm modules so that no transpiler is necessary.