react-code-dataset / next.js /docs /01-app /03-api-reference /05-config /01-next-config-js /generateBuildId.mdx
Download next.js/docs/01-app/03-api-reference/05-config/01-next-config-js/generateBuildId.mdx from Devendra174/react-code-dataset: direct link, hf CLI and curl.
- Browser
- Download file 947 Bytes
-
https://huggingface.co/datasets/Devendra174/react-code-dataset/resolve/main/next.js/docs/01-app/03-api-reference/05-config/01-next-config-js/generateBuildId.mdx
- Command line
-
hf download hf://datasets/Devendra174/react-code-dataset/next.js/docs/01-app/03-api-reference/05-config/01-next-config-js/generateBuildId.mdx
-
curl -L -o generateBuildId.mdx https://huggingface.co/datasets/Devendra174/react-code-dataset/resolve/main/next.js/docs/01-app/03-api-reference/05-config/01-next-config-js/generateBuildId.mdx
947 Bytes
| --- | |
| title: generateBuildId | |
| description: Configure the build id, which is used to identify the current build in which your application is being served. | |
| --- | |
| {/* The content of this doc is shared between the app and pages router. You can use the `<PagesOnly>Content</PagesOnly>` component to add content that is specific to the Pages Router. Any shared content should not be wrapped in a component. */} | |
| Next.js generates an ID during `next build` to identify which version of your application is being served. The same build should be used and boot up multiple containers. | |
| If you are rebuilding for each stage of your environment, you will need to generate a consistent build ID to use between containers. Use the `generateBuildId` command in `next.config.js`: | |
| ```jsx filename="next.config.js" | |
| module.exports = { | |
| generateBuildId: async () => { | |
| // This could be anything, using the latest git hash | |
| return process.env.GIT_HASH | |
| }, | |
| } | |
| ``` | |