Nuxt3/Vue3 in production is reporting many instances of Cannot find static asset /_nuxt/<filename>.<hash>.js

[technoY2K]

Hello everyone. We have a website deployed and are getting thousands of reports that assets cannot be found. The assets are JavaScript chunks, CSS, etc. The site works with no issues, however, the server instance is throwing errors which we pinned down to Nitro server code: My hypothesis is that for some reason the server is looking for older hashed files which wouldn't exist since every time we deploy, new hashed files are uploaded.

if (!asset) {
    if (isPublicAssetURL(id)) {
      removeResponseHeader(event, "Cache-Control");
      throw createError$1({
        statusMessage: "Cannot find static asset " + id,
        statusCode: 404
      });
    }
    return;

My question is 2 fold.

1. Could someone possibly explain what is happening?

2. What are some steps we could take to possibly mitigate these errors.

[manniL]

My hypothesis is that for some reason the server is looking for older hashed files which wouldn't exist since every time we deploy, new hashed files are uploaded.

That sounds reasonable, yes.

Could someone possibly explain what is happening?

Most likely that, after a new deploy, current visitors still request older static assets of your site

What are some steps we could take to possibly mitigate these errors.

Save them e.g. via CDN and cache them on the server forever.

[technoY2K]

Hello, do you mean to save the old hashed files along side the new deployed files that are created under .output?

[zestlee1106]

Hello, I have the same issue with my project, did you solve it?

[existe-deja]

I'm working on this solution and you should take a look at https://nuxt.com/docs/api/composables/use-runtime-config#appcdnurl

[technoY2K]

Hey @zestlee1106 , we ended up just switching over to AWS Amplify to avoid the issue all together.