Replies: 1 comment 7 replies
-
I remember someone asked this way before, a few years back perhaps, and they reported back that it had caused some issues. Let me find it for you. |
Beta Was this translation helpful? Give feedback.
7 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Summary
I'm using the next 14.2.13 version, and it's an SSG build environment through
output: 'export'
setting.There is a limit to the number of files when deploy on my company system,
I want to fix buildId by modifying the next.config.js file as below.
In this process, I am considering settings because I am worried about cache processing.
I plan to set the
Cache-Control: no-cache, no-store
header to respond to the two files in case/out/static/fixedBuildId/_buildManifest.js
and/out/static/fixedBuildId/_ssgManifest.js
change during the build path.Other than this, are there any additional side effects from fixing buildId?
Additionally, it seems that the list of chunks for pages written in the past
_buildManifest.js
is written at{path}.txt
in each path, but doesn't the txt file also need aCache-Control
header?Additional information
No response
Example
No response
Beta Was this translation helpful? Give feedback.
All reactions