You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues of this repository and believe that this is not a duplicate.
I built my Next app and deployed it as I usually do, but when loading the page, I got the following on the browser:
Uncaught ReferenceError: webpackJsonp is not defined in main.js 1:1
Also, all JS interactivity was broken, but the style/design of the website was looking okay.
Here is the beginning of main.js file:
module.exports=webpackJsonp([0],{
I rebuilt and redeployed the application and it disappeared.
I believe it is because I had a running Next.js app while building, and I was changing the code on it, which trigger other rebuilds. It probably messed up the build process (the first main.js wasn't uglified at all, while the new/fixed version I have now is correctly uglified/onelined)
I'm reporting the issue because I could have not noticed it, maybe something should be done when a build is ran when another build is in process. The main issue is deploying a non-working app to production without noticing it. I agree that's a very particular use case, which is very hard to reproduce. People shouldn't be building while doing modification to the source code with a watcher enabled. =D
The text was updated successfully, but these errors were encountered:
I built my Next app and deployed it as I usually do, but when loading the page, I got the following on the browser:
Uncaught ReferenceError: webpackJsonp is not defined
in main.js 1:1Also, all JS interactivity was broken, but the style/design of the website was looking okay.
Here is the beginning of main.js file:
I rebuilt and redeployed the application and it disappeared.
I believe it is because I had a running Next.js app while building, and I was changing the code on it, which trigger other rebuilds. It probably messed up the build process (the first main.js wasn't uglified at all, while the new/fixed version I have now is correctly uglified/onelined)
I'm reporting the issue because I could have not noticed it, maybe something should be done when a build is ran when another build is in process. The main issue is deploying a non-working app to production without noticing it. I agree that's a very particular use case, which is very hard to reproduce. People shouldn't be building while doing modification to the source code with a watcher enabled. =D
The text was updated successfully, but these errors were encountered: