fix: Use .esm.js module for backwards compatibility with old build tools #939
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some people have reported trouble with the new release of immer, in particular in #937 and #921. The reason seems to be that older build tools are having trouble to understand
.mjs
files as JavaScript.Since currently immer publishes both an
.esm.js
and.esm.mjs
bundle (introduced in #921), with the whole purpose of being backwards compatible, in this pull request I'm reverting themodule
and other fields inpackage.json
to using the.esm.js
bundle, while only theexports
field uses the.esm.mjs
bundle. I'm hoping that this will achieve both compatibility with Node.js as well as ancient build tools.