Nuxt.js: want to hook on page component js import error

[igtm]

nuxt page component js filename changes every time we use npm build

Considering deployment, for example, if a user uses our nuxt app and then we build and deploy new nuxt app, the user no longer be able to go to next page by SPA because the next page component js filename changes and no longer import and render. it's not good...

i would say one idea avoiding this problem is support for adding custom hook on page component js import error. (for example, refresh the browser)

any ideas ??

_{This feature request is available on Nuxt.js community (#c2001)}

[clarkdo]

The hash of filename in calculated from content of component file, it will be changed only when content of file is changed.

In development, every change will lead to a dev rebuilding and hot-replacing and file will be replaced.

In production, every change should be deployed by rebuilding and restarting and users will access new files directly.

What are your specific operating steps ?

[igtm]

Thanks your response.

We use ECS (AWS) for operating Nuxt app.
So when deploying our new version app, the app is fully replaced.

So again, if there are some users that still use old version app when we switch old version app to new version app, the users fail to go to next page by spa(nuxt-link tag) if the next page component js filename changes...

If our app should be deployed very frequently (for example, thousands in a day), many users will encounter to the problem. It’s very bad for UX...

Any solutions??

[igtm]

note: page components are imported dynamically (on SPA). so if the js file is 404, the nuxt app on client browser cannot render the next page and throw error.

[clarkdo]

/cc @Atinux @pi0

[Atinux]

Hi @igtm

Indeed we may work on this issue to reload the app if the chunk is not found.

[hanjeahwan]

Our production facing this issue also when keep update to live server , load chunk fail 😣

[manniL]

Further discussion on https://github.com/nuxt/nuxt.js/issues/3389

[lock[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.