mirror of
https://github.com/hanzoai/next.js.git
synced 2026-09-24 17:00:51 +00:00
Niklas MischkulnigandGitHub
0aac540416
Closes PACK-6536 - with deployment id available: a header contains the process.env.NEXT_DEPLOYMENT_ID , the client knows its dpl id already, so we can use that already - with deployment id unavailable: a response field contains the BUILD_ID, keep the existing logic of storing the build id in the browser It's unfortunate that we have to keep the BUILD_ID response field approach as a fallback, but oh well. This has the benefit that we won't need the build id anymore when the deployment id is available. If you use `output:export` and set `config.deploymentId` (i.e. enable skew protection) you are still expected to set these headers. --- - [x] Fallback behavior for when there is no deployment id - [ ] Run deployment tests
20 lines
414 B
JavaScript
20 lines
414 B
JavaScript
const buildId = process.env.NEXT_PUBLIC_BUILD_ID
|
|
if (!buildId && !process.env.NEXT_DEPLOYMENT_ID) {
|
|
throw new Error('Neither NEXT_PUBLIC_BUILD_ID nor NEXT_DEPLOYMENT_ID is set')
|
|
}
|
|
|
|
/**
|
|
* @type {import('next').NextConfig}
|
|
*/
|
|
const nextConfig = {
|
|
distDir: '.next' + (process.env.DIST_DIR || ''),
|
|
|
|
generateBuildId:
|
|
buildId &&
|
|
(async () => {
|
|
return buildId
|
|
}),
|
|
}
|
|
|
|
module.exports = nextConfig
|