fix(next-config): guard BLOB_STORE_ID in images.remotePatterns #491
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 Next.js crash when
BLOB_STORE_IDis missingSummary
Fixes a Next.js startup crash caused by an invalid
images.remotePatternsentrywhen
BLOB_STORE_IDis not defined.Context
On a clean setup,
next.config.jsalways added an image remote pattern usingprocess.env.BLOB_STORE_ID, resulting in an invalid hostname and causingNext.js strict config validation to fail.
This issue was previously reported in #417,
where the suggested workaround was to manually define a dummy
BLOB_STORE_ID.Changes
BLOB_STORE_IDimage host only when the env variable is definedremotePatternsentries on fresh installsTesting
pnpm devwithoutBLOB_STORE_IDpnpm devwithBLOB_STORE_IDsetpnpm buildRelated