You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some background: we use next.js with a custom express server & have cloudfront configured to hit the next.js app.
Was wondering if the contents of the "out" folder after doing next build && next export can safely be cached "forever"?
Had some concerns since I don't see a hash on some of the files..
For example: the [0-3].js chunks:-
The specific issue we're having is that after a new deployment, some users start seeing 404s on the old server's assets (since that server is brought down).
Came across this gist but not sure if this is up to date!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hey guys!
Some background: we use next.js with a custom express server & have cloudfront configured to hit the next.js app.
Was wondering if the contents of the "out" folder after doing
next build && next export
can safely be cached "forever"?Had some concerns since I don't see a hash on some of the files..
For example: the
[0-3].js
chunks:-The specific issue we're having is that after a new deployment, some users start seeing 404s on the old server's assets (since that server is brought down).
Came across this gist but not sure if this is up to date!
Beta Was this translation helpful? Give feedback.
All reactions