-
Notifications
You must be signed in to change notification settings - Fork 651
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support esm via package.json routes #488
Conversation
Ref reactjs#77 Upgraded semantic-release-alt-publish-dir to get correct module field processing jquense/semantic-release-alt-publish-dir@795af9d
same as #455 this is fine; we'll need to note the breaking change for semver |
what is the breaking change again? |
Here's a breaking change |
@jquense it's #475 (comment) if you have a CJS module that imports the ESM build due to the inter-op, then you will actually get the ESM module this time around, which means you'll need to add the |
# [4.0.0](v3.0.0...v4.0.0) (2019-04-16) ### Features * support esm via package.json routes ([#488](#488)) ([6337bf5](6337bf5)), closes [#77](#77) ### BREAKING CHANGES * in environments where esm is supported importing from commonjs requires explicitly adding the `.default` after `require()` when resolving to the esm build
🎉 This PR is included in version 4.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
# [4.0.0](reactjs/react-transition-group@v3.0.0...v4.0.0) (2019-04-16) ### Features * support esm via package.json routes ([#488](reactjs/react-transition-group#488)) ([6337bf5](reactjs/react-transition-group@6337bf5)), closes [#77](reactjs/react-transition-group#77) ### BREAKING CHANGES * in environments where esm is supported importing from commonjs requires explicitly adding the `.default` after `require()` when resolving to the esm build
# [4.0.0](reactjs/react-transition-group@v3.0.0...v4.0.0) (2019-04-16) ### Features * support esm via package.json routes ([#488](reactjs/react-transition-group#488)) ([6337bf5](reactjs/react-transition-group@6337bf5)), closes [#77](reactjs/react-transition-group#77) ### BREAKING CHANGES * in environments where esm is supported importing from commonjs requires explicitly adding the `.default` after `require()` when resolving to the esm build
# [4.0.0](reactjs/react-transition-group@v3.0.0...v4.0.0) (2019-04-16) ### Features * support esm via package.json routes ([#488](reactjs/react-transition-group#488)) ([6337bf5](reactjs/react-transition-group@6337bf5)), closes [#77](reactjs/react-transition-group#77) ### BREAKING CHANGES * in environments where esm is supported importing from commonjs requires explicitly adding the `.default` after `require()` when resolving to the esm build
# [4.0.0](reactjs/react-transition-group@v3.0.0...v4.0.0) (2019-04-16) ### Features * support esm via package.json routes ([#488](reactjs/react-transition-group#488)) ([6337bf5](reactjs/react-transition-group@6337bf5)), closes [#77](reactjs/react-transition-group#77) ### BREAKING CHANGES * in environments where esm is supported importing from commonjs requires explicitly adding the `.default` after `require()` when resolving to the esm build
Ref #77
Upgraded semantic-release-alt-publish-dir to get correct module field
processing
jquense/semantic-release-alt-publish-dir@795af9d