fix(@formatjs/ts-transformer): restore ts-jest-integration import#6433
Closed
azolotopup wants to merge 1 commit intoformatjs:mainfrom
Closed
fix(@formatjs/ts-transformer): restore ts-jest-integration import#6433azolotopup wants to merge 1 commit intoformatjs:mainfrom
azolotopup wants to merge 1 commit intoformatjs:mainfrom
Conversation
longlho
requested changes
Apr 24, 2026
…ken by exports field
This was referenced Apr 24, 2026
Member
|
Thanks for the report! I've opened #6437 with a more complete fix that also adds |
dzbarsky
pushed a commit
to dzbarsky/formatjs
that referenced
this pull request
Apr 26, 2026
…port (formatjs#6437) ## Summary - Add `./ts-jest-integration.js` to the `exports` field in `package.json` - Add `ts-jest-integration.ts` as a rolldown entry point in `BUILD.bazel` so it gets bundled with `.js`, `.d.ts`, and `.js.map` into the published package - Update jest integration test config to use `.js` extension in the import path This was a regression from formatjs#6080 which added an `exports` field to `package.json` but only included `.` — blocking the `ts-jest-integration` deep import that ts-jest users rely on. Closes formatjs#6433 ## Test plan - [x] `bazel test //packages/ts-transformer:package_exports_test` — validates all exports resolve to real files - [x] `bazel test //packages/ts-transformer:unit_test` — 27 tests pass - [x] All pre-commit hooks pass 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-authored-by: Claude Opus 4.6 (1M context) <[email protected]>
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
2 participants
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.
PR #6080 added
"exports": { ".": "./index.js" }to@formatjs/ts-transformer, which inadvertently broke the ts-jest-integration deep import that ts-jest users rely on for AST transformer configuration.Problem
After upgrading to
@formatjs/[email protected], any project usingts-jestwith the formatjs ast transformer fails before tests execute with error:File not found: @formatjs/ts-transformer/ts-jest-integrationThis affects the documented ts-jest configuration pattern:
Fix
Expose
ts-jest-integrationas an explicit subpath exportImpact
No breaking changes — existing "." export is unchanged
Restores the documented ts-jest integration path without requiring any workaround on the consumer side
ts-jest-integration.js already exists in the published package; this change only makes it reachable via the exports map
Related
Regression introduced by: #6080