fix: prevent Turbopack build failures when importing harness-claude-code - #19985
Closed
ai-sdk-factory[bot] wants to merge 3 commits into
Closed
fix: prevent Turbopack build failures when importing harness-claude-code#19985ai-sdk-factory[bot] wants to merge 3 commits into
ai-sdk-factory[bot] wants to merge 3 commits into
Conversation
Co-authored-by: brightiron <95196612+brightiron@users.noreply.github.com>
1 task
Collaborator
|
worse version of #20033 |
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
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.
Background
Importing the published @ai-sdk/harness-claude-code package in a Next.js 16 server route caused the default Turbopack production build to fail.
Root Cause
The bootstrap code emitted a ../bridge/ asset candidate that points outside the published dist/bridge directory; the packaged Next.js reproduction confirmed Turbopack statically rejected that nonexistent path.
Summary
Bridge assets now resolve only beside the source or bundled module, removing the invalid fallback path. Added a patch changeset and removed reproduction-only artifacts.
Testing
Added regression coverage verifying bridge assets resolve correctly from both source and bundled module layouts.
End-to-end Validation
pnpm -C examples/ai-functions exec tsx src/reproduction/issue-19982.tsvia immutable replay: packaged Next.js 16.3.3 Turbopack build succeeded without externalizing the package.Related Issues
Fixes #19982
Closes #19983