Debugging `Application error: a client-side exception has occurred` in staging environment
Unanswered
Large garden bumble bee posted this in #help-forum
Large garden bumble beeOP
Hello, I am currently running into a problem where when I kill the cache and reload one of my pages in staging, it appears to encounter a client side issue. This only occurs in staging, and not when I try to replicate locally
The error:
In the console, I see the following error:
However, since it is minified, it's very hard to inspect where or why this is happening.
I've tried rebuilding the app in staging, but the same issue occurs. I'm wondering if there's a good way to debug this, perhaps I should set minification to false and see what happens? Can this be done with an environment variable?
The error:
Application error: a client-side exception has occurred (see the browser console for more information).In the console, I see the following error:
7023-fd0bbd7f61705137.js:1 ChunkLoadError: Loading chunk 7018 failed.However, since it is minified, it's very hard to inspect where or why this is happening.
I've tried rebuilding the app in staging, but the same issue occurs. I'm wondering if there's a good way to debug this, perhaps I should set minification to false and see what happens? Can this be done with an environment variable?
5 Replies
@Large garden bumble bee Hello, I am currently running into a problem where when I kill the cache and reload one of my pages in staging, it appears to encounter a client side issue. This _only_ occurs in staging, and not when I try to replicate locally
The error:
Application error: a client-side exception has occurred (see the browser console for more information).
In the console, I see the following error:
7023-fd0bbd7f61705137.js:1 ChunkLoadError: Loading chunk 7018 failed.
However, since it is minified, it's very hard to inspect where or why this is happening.
I've tried rebuilding the app in staging, but the same issue occurs. I'm wondering if there's a good way to debug this, perhaps I should set minification to false and see what happens? Can this be done with an environment variable?
can you stop your app, delete the .next folder and the node_modules folder and then hit
npm install to install your node modules back and start your app. Do you still see the error?Large garden bumble beeOP
I'll try locally
hmmm... so when I do that locally it doesn't recreate the problem. Yesterday, I tried rebuilding it from scratch (basically just by triggering pipelines again)
Large garden bumble beeOP
actually, I think I found why. It wasn't next.js's problem