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
What's the correct approach to deal with a CDN? Should I upload my
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/23612
app:chunkErrorWhat's the correct approach to deal with a CDN? Should I upload my
/_nuxtI 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/23612
GitHub
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
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)
