Add missing env inlining and hash replacing for standalone mode #85262
+10
−0
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.
Fix #80194.
This adds the missing env inlining and hash replacing for standalone mode bundled by webpack. This issue does not occur in turbopack mode because
generate-envis not involved.To reproduce, please clone https://github.com/hood/nextjs-env-repro. And change the build script to:
This repository uses
next@15.3.3, I added--webpackto ensure it works as expected in the latestnext@16.0.0since the default bundler is changed to Turbopack now.Then run:
pnpm build && node .next/standalone/server.jsThe expected result is the NEXT_PUBLIC_ environment varaible is defined for client component.
The actual result is it's
undefined, because the referenced js file path (hash) in standalone directory is not correct anymore aftergenerate-env.