Add support for Node ESM #4038
Add support for Node ESM #4038
Conversation
# Conflicts: # examples/rsp-next-ts/next.config.mjs
…SM-again # Conflicts: # package.json
|
Build successful! 🎉 |
|
Build successful! 🎉 |
|
## API Changes
unknown top level export { type: 'identifier', name: 'Column' } |
|
🎉 congrats @devongovett and @snowystinger ! |
|
as the issue is already closed and merged, is there a patch release estimate? |
|
@abdulhdr1 if it helps, there are nightly releases of |
|
When will this reach packages like |
|
This will be released in the next week. Hold tight! |
Closes #2881
This re-adds support for Node ESM after it was reverted in #3839 due to breaking webpack 4. Now we use a new strategy which distributes three files for each module:
dist/main.js– the CommonJS version in the "main" field, used by node when required, jest, etc.dist/module.js– the legacy ESM version in the "module" field, used by webpack 4 and other tools that don't support package.json exports. This is needed because.mjsdoesn't work properly in webpack 4.dist/import.mjs– the modern ESM version in the "exports.import" field, used by Node and other tools supporting exports. This is the exact same asdist/module.jsbut with the.mjsextension for Node.I also tried using
"type": "module"in package.json to avoid the third entry point, but this broke other things since it applies to all.jsfiles and not just thedistdirectory.The icons now distribute two versions each:
IconName.js– the CommonJS versionIconName.module.mjs– the ESM version. This is specially not namedIconName.mjsso that webpack 4 does not try to resolve it and then fail to resolve the imports. Only tools that support package.json exports will resolve this file.