How to avoid chunkError on new deploy?
Every new deploy replace the old one, but there is still some user navigating on the app. I know about the
app:chunkError mechanism, but I want to implement the CDN way @Atinux is explaining here > https://github.com/nuxt/nuxt/issues/742#issuecomment-393773038
What's the correct approach to deal with a CDN? Should I upload my /_nuxt folder somewhere and what is the infra setup to handle them? Shoud I specify to the running app to serve them also?
I think an article is the doc would help many people.
related issues :
experimental emitRouteChunkError https://github.com/nuxt/nuxt/issues/23612
chunkError on lazy loaded components https://github.com/nuxt/nuxt/issues/23612GitHub
handle chunk loading errors that are not triggered by navigation · ...
Describe the feature When a chunk has been given a new name during build as it has changed, some clients will try to load the old chunk name. This results in errors like: TypeError: error loading d...
GitHub
Loading chunk {n} failed · Issue #742 · nuxt/nuxt
Hello, when loading the page, there is an error loading chunk {n} (n - some number) failed how to fix it? Thanks in advance! This bug report is available on Nuxt.js community (#c636)
2 Replies
GitHub
handle chunk loading errors that are not triggered by navigation · ...
Describe the feature When a chunk has been given a new name during build as it has changed, some clients will try to load the old chunk name. This results in errors like: TypeError: error loading d...
Yes, I rewrote a solution based on what I found from different issues. But my point is how to avoid it at all and guarantee chunk availability.