TypeError: Failed to fetch dynamically imported module _nuxt/login

[dungonfq]

Environment

Production

Reproduction

Describe the bug

My app on Production is facing many issues Failed to fetch dynamically imported module or 403 issue. This is how Sentry log the error:

Luckily, this error doesn't break the application. My website still runs normally while Chrome's Devtool is logging the error.

Have anyone faced the same issue and have idea to fix it?

Thank all.

Additional context

No response

Logs

No response

[manniL]

Does the time of the errors correlate with new deployments? If so, it could be #3389

[danielroe]

I do sometimes get:

which triggers a 404 page:

How are you hosting your site? Is there any reason your static assets are behind auth?

[dungonfq]

@manniL Yes, it usually happens after new deployments

[dungonfq]

@danielroe Yes, we can't get the module because of a 403 error, It redirects u to the error page (404).

I don't do the DevOp stuff so can not give u details on how we're hosting the site. In short, we're using Jenkin to build & deploy Production with Docker, and run it on a Docker image. We push the container images to an Amazon ECR repository.

[dungonfq]

Found the root cause by the rate limit of my server.

I created another issue for the solution on Nuxt side: #14093

[liya-zi]

I encountered the same problem after deployment，What should I do

[dungonfq]

@ziyali
my issue is Nuxt loads too many modules at a time. On PROD, the site fetches & prefetches > 100 requests per second which exceed our server's rate limit (100r/s). Therefore, some of my modules cannot load "Failed to fetch...".

The rate limit also happens if users access the page at the same time & send too many requests.

If u're facing the same problem u can try troubleshooting ur rate limit by turning it off. There's is nothing to do for now, we have to wait. You can keep track the solution with Nuxt here: #13778

Cheers

[Tyki]

Hi @danielroe, any updates on this issue?

We are having a ton of these errors every day for a large domain driven app built with Nuxt 3.2

[danielroe]

@Tyki There can be multiple causes for this. If it's related to new deployments, have you tried using the new experimental.emitRouteChunkError option? #19038

If not, would you open a new issue with a reproduction? 🙏