fix: support @next/env without default export on Next.js 15.5+#16675
Open
rachit367 wants to merge 1 commit into
Open
fix: support @next/env without default export on Next.js 15.5+#16675rachit367 wants to merge 1 commit into
rachit367 wants to merge 1 commit into
Conversation
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.
Fixes #16674.
On Next.js 15.5+,
@next/envno longer ships adefaultexport — only named exports remain.bin/loadEnv.tsdoesimport nextEnvImport from '@next/env'and thenconst { loadEnvConfig } = nextEnvImport, which throwsTypeError: Cannot destructure property 'loadEnvConfig' of 'import_env.default' as it is undefined.whenever the module is loaded through interop paths (e.g. running scripts viatsx).Switching to a namespace import and falling back from
.defaultto the namespace itself keeps both shapes working:nextEnvImport.defaultisundefined, so we destructure from the namespace.nextEnvImport.defaultis the legacy CJS default object, so we destructure from that (matches the previous behaviour).The patch is exactly what the issue proposes.