fix: guarantee Next's native swc binary in the prod Docker build - #2
Merged
Conversation
npm ci intermittently omits the platform-optional @next/swc-linux-*-gnu native dep even when it's correctly in the lockfile (npm/cli #4828). Next 16's Turbopack has no WASM fallback, so a missing binary aborts the build. Force-install the arch-matching binary after npm ci so the build no longer depends on npm-ci luck. Same fix already shipped in shell v0.2.2. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Force-install Next's arch-matching native swc binary after
npm ciso the prod Docker build no longer depends on the npm-ci optional-deps flake (npm/cli #4828). Next 16's Turbopack has no WASM fallback, so a missing binary aborts the build. Verified locally (arm64): Turbopack✓ Compiled successfully. Same fix already shipped in shell v0.2.2.🤖 Generated with Claude Code