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
Then I ran it again, the bug was gone, but I got new error
{ Error: ENOENT: no such file or directory, open '/opt/www/eefd7f76-3b2c-4abe-b8d9-14399006a068/.next/app.js'
at Error (native)
errno: -2,
code: 'ENOENT',
syscall: 'open',
path: '/opt/www/eefd7f76-3b2c-4abe-b8d9-14399006a068/.next/app.js' }
I've checked for it in eefd7f76-3b2c-4abe-b8d9-14399006a068 folder, there is no app.js file but a main.js file.
Why it looked for app.js but not main.js?
Here is the folder:
Your Environment
Tech
Version
next
3.2.2
webpack
3.8.1
The text was updated successfully, but these errors were encountered:
Hello, everyone, I'm about deploying my nextjs application to production, but I can not run build "npm run build" command which will run "next build"
Expected Behavior
A folder with random name is generated for production
Current Behavior
The first time, I got an error
so I created next.config.js file with following contain:
Then I ran it again, the bug was gone, but I got new error
I've checked for it in eefd7f76-3b2c-4abe-b8d9-14399006a068 folder, there is no app.js file but a main.js file.
Why it looked for app.js but not main.js?
Here is the folder:
Your Environment
The text was updated successfully, but these errors were encountered: