TXT files used for prefetch are not handled properly in static deploys #62739
Labels
bug
Issue was opened via the bug report template.
invalid link
The issue was auto-closed due to a missing/invalid reproduction link. A new issue should be opened.
Navigation
Related to Next.js linking (e.g., <Link>) and navigation.
Link to the code that reproduces this issue
not applicable
To Reproduce
export: 'static'
Current vs. Expected behavior
.txt artifacts are created for what it seems to be a prefetching strategy and these files names are un-versioned (or un-hashed) into the root where the page can be found. Because of this, these files can't be cached or otherwise an update on the overall site will result in a broken state where chunks are not found and a browser force pull is needed.
This is the part of the code that tries to solve for the cdn case but on static deploys this doesn't really change and the url + parameter ends up always being the same.
In our case that hash ends up being:
Provide environment information
Which area(s) are affected? (Select all that apply)
App Router, Routing (next/router, next/navigation, next/link)
Which stage(s) are affected? (Select all that apply)
Other (Deployed)
Additional context
No response
The text was updated successfully, but these errors were encountered: