fix(@formatjs/intl-numberformat)!: convert to ESM#5431
Closed
longlho wants to merge 1 commit intographite-base/5431from
Closed
fix(@formatjs/intl-numberformat)!: convert to ESM#5431longlho wants to merge 1 commit intographite-base/5431from
longlho wants to merge 1 commit intographite-base/5431from
Conversation
This was referenced Dec 14, 2025
Closed
Member
Author
|
Warning This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has required the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Dec 14, 2025
graphite-app bot
pushed a commit
that referenced
this pull request
Dec 14, 2025
### TL;DR Convert `intl-numberformat` package to ESM format. ### What changed? - Added `"type": "module"` to package.json - Added proper exports configuration in package.json - Updated all import paths to include `.js` extensions - Skipped CJS build in Bazel configuration - Updated import references in react-intl examples to use `.js` extensions ### How to test? 1. Build the package with `yarn build` 2. Verify that the package works correctly in ESM environments 3. Test the react-intl examples to ensure they still function properly 4. Verify that polyfills can still be imported correctly ### Why make this change? This change modernizes the `intl-numberformat` package by converting it to use ES Modules natively. This improves compatibility with modern JavaScript tooling and bundlers while maintaining the same functionality. The change is part of a broader effort to update FormatJS packages to use ESM.
Merge activity
|
graphite-app bot
pushed a commit
that referenced
this pull request
Dec 14, 2025
### TL;DR Convert `intl-numberformat` package to ESM format. ### What changed? - Added `"type": "module"` to package.json - Added proper exports configuration in package.json - Updated all import paths to include `.js` extensions - Skipped CJS build in Bazel configuration - Updated import references in react-intl examples to use `.js` extensions ### How to test? 1. Build the package with `yarn build` 2. Verify that the package works correctly in ESM environments 3. Test the react-intl examples to ensure they still function properly 4. Verify that polyfills can still be imported correctly ### Why make this change? This change modernizes the `intl-numberformat` package by converting it to use ES Modules natively. This improves compatibility with modern JavaScript tooling and bundlers while maintaining the same functionality. The change is part of a broader effort to update FormatJS packages to use ESM.
graphite-app bot
pushed a commit
that referenced
this pull request
Dec 14, 2025
### TL;DR Convert `intl-numberformat` package to ESM format. ### What changed? - Added `"type": "module"` to package.json - Added proper exports configuration in package.json - Updated all import paths to include `.js` extensions - Skipped CJS build in Bazel configuration - Updated import references in react-intl examples to use `.js` extensions ### How to test? 1. Build the package with `yarn build` 2. Verify that the package works correctly in ESM environments 3. Test the react-intl examples to ensure they still function properly 4. Verify that polyfills can still be imported correctly ### Why make this change? This change modernizes the `intl-numberformat` package by converting it to use ES Modules natively. This improves compatibility with modern JavaScript tooling and bundlers while maintaining the same functionality. The change is part of a broader effort to update FormatJS packages to use ESM.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
TL;DR
Convert
intl-numberformatpackage to ESM format.What changed?
"type": "module"to package.json.jsextensions.jsextensionsHow to test?
yarn buildWhy make this change?
This change modernizes the
intl-numberformatpackage by converting it to use ES Modules natively. This improves compatibility with modern JavaScript tooling and bundlers while maintaining the same functionality. The change is part of a broader effort to update FormatJS packages to use ESM.