Repository navigation
Create an explainer / hub page for unflagged require(ESM) support #35
Description
Activity
Thanks for opening the issue! I think this is what part of the package-examples aim to solve (e.g. in the Making ESM require-able chapter, the goal is to have some actual working examples there living side by side with the document), though this is still a WIP and I have not gotten to filling in the skeletons already laid out in there. Feel free to take a look at https://github.com/nodejs/package-examples/blob/main/CONTRIBUTING.md if anyone is interested ;)
Reacted by Claudio Wunder, Augustin Mauroy and Josh Ghoulberg 👻@JoshuaKGoldberg please assign me this issue
Hi! You are more than welcome to work on resolving this issue, we'd actually really appreciate it!
However, we don't typically assign issues to users.
FYI I opened nodejs/package-examples#16 to add a CJS->ESM migration guide in the package example guide, which, together with the chapter 3-4 landed there before, should include all the points suggested in the OP.
Reacted by Josh Ghoulberg 👻, Augustin Mauroy and Claudio WunderReacted by Josh Ghoulberg 👻, Augustin Mauroy and Claudio Wunder
Enter your suggestions in details:
The new unflagged require(ESM) support in Node.js is very exciting. It's starting to let a lot of tools move to ESM without feat of leaving dependents behind. 🚀
But, there isn't one single high-level, official resource I can find that users can be pointed to to understand the unflagged support.
Proposal: can the Node.js site have a page added dedicated to the unflagged require(ESM) support? I'd imagine it could contain:
^20.19.0 || >=22.12.0seems to be the common support target post-18.xSibling issue to #34, intentionally with as similar an issue body as possible.