Error: ENOENT: no such file or directory, open 'E:\projects\almostwiki\my-app\test\my-app\.next\BUILD_ID'

[LLytho]

Link to the code that reproduces this issue

https://github.com/LLytho/ENOENT-next

To Reproduce

1. npx create-next-app@latest
2. cd my-app
3. npm run build
4. npm run start

Results into:

[Error: ENOENT: no such file or directory, open 'E:\projects\almostwiki\my-app\.next\BUILD_ID'] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'open',
  path: 'E:\\projects\\almostwiki\\my-app\\.next\\BUILD_ID'
}

Using npm run dev also just cancels. No log file given or any error.

Tried with Node 18.18 LTS and Node 20 with npm 9, 10 and yarn.
The issue mainly happens on Next 13.5.x and canary. I tried downgrading to 13.4.x but then after npm run dev i only get info Using wasm build of next-swc and it also cancels directly.

Current vs. Expected behavior

I'm excepting that next runs

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
  Platform: win32
  Arch: ia32
  Version: Windows 11 Enterprise
Binaries:
  Node: 18.18.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 13.5.5
  eslint-config-next: 13.5.5
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Additional context

No response

[salman0ansari]

did you solved this?

[LLytho]

Sadly not. I tried 14 too but now I got other issues there with SWC even if I disable SWC through next config.

[Galacticai]

same on ubuntu <- proot-distro <- termux <- android 13 aarch64
problem exists in a fresh project, using the latest stable version of next that npm provides

why is this discussion when it seems like a bug

[salman0ansari]

Instead of fixing bugs they are releasing new versions

[Galacticai]

[LLytho]

It was an issue but it got converted to a discussion

[Mitsune-e]

That is why is called Next
Sorry for the Necro but still happening

[flacial]

@Galacticai nah, what's blud doing lurking in the deep, dark, and lonely depths of js's tools?

[cejblan]

It also gives me that error. did you solve?

[salman0ansari]

I upgraded server ram from 2gb to 4gb and it worked.

[cejblan]

I understand, my server already has 4GB of ram, maybe cleaning it is the solution

[Galacticai]

What about my 8gb ram device having the same issue

[cejblan]

I had the same criteria, it shouldn't affect because I shouldn't need more than 1GB of ram. In vercel it works perfectly for me, but on the server with cpanel it doesn't

[lovebes]

... wait what has memory got to do with a missing file?

[SameeraLakshithaPerera]

This work for me :

1. update node and next latest version.
2. npm uninstall next
3. npm install next
4. npm run build
5. npm run start

[charozel]

Thanks, this worked for me!

[abdullohmirzayev]

Thank you so much

[edunavajas]

God bless you

[barrosanapaulas]

when i'm trying use with yarn, doesn't not work for me.. but, when i changed the package manager to npm, it's worked fine..

[tanshiyu1999]

This actually worked for me, thank you.

[armanTakmazyan]

It fails exactly during the build stage and I see the same error message.

[mladentsvetkov]

Hi there, in my case, brand new installation, enough RAM, latest node, all is ok.
So I believe the problem is somewhere else.

[jdavmosafefleet]

In my case the issue was present during the npm run start, after run npm run build, it works

[namgold]

This worked for me. yarn build/npm run build first to initialize the folders then yarn start/npm run start should worked

[Vikash174]

Yes, it worked for me

[binarytrance]

Yup! this worked.

[Jmencos]

NPM run build solved this issue for me as well!

[Xiaojiju]

It worked for me,thx, U saved me!

[caceresjayder]

I have my web page on azure, the problem was happen when I set the option

output: 'export',

In the next.config.js to generate a static export of the page.

In the distDir you only going to have static asset's for the page and not a next.js application,

If you are not going to use a static page web server, you can deactivate it.

You won't get that error again while executing npm run start because with npm run build next gonna build a next app instead of a static webpage...

[levonsamvelyan]

In my case, the problem was with the "Prettier" library, which threw an error on the "npm run build" command because of semicolons:

You can either add semicolons in the files mentioned in the error, or you can add this rule to the ".eslintrc.json" file:
{ "extends": "next/core-web-vitals", "rules": { "prettier/prettier": ["error", { "semi": false }] } }
After that, run the "npm run build" command again. It should compile without errors, and other commands will also start working.

[alvinChristianto]

i have the same problem in my staging vps server, and i try this :

1. fetch and merge changes
2. npm run build
3. pm2 restart [id]

note i use pm2. also i checked pm2 logs [id] and tailing /etc/nginx/error

[abhimohpra]

I am facing same issue. Is it RAM related problem as some people suggested? Will it not work with 1GB RAM?

[abhimohpra]

As a workaround: We are building production build our project at local system (4GB RAM) and then deploying ".next" to server and node_modules we have separately installed at server. So far it's working, don't know how long. We are not running build command at server.

[ayushshrestha]

I also did lots of research and found this but npm run start and then npm run build might not go quick solution....
First i did NPM run build and then when file is exported on necessary file and then I tried to do NPM run start after that it works well :)

[mhdalaa93]

https://github.com/vercel/next.js/discussions/58523

as per the above link, the issue might be solved by increasing RAM.

[ayushshrestha]

I am using M1 Macbook Pro 16GB Ram. do you still think that because of RAM ?

[alricliew]

I found a workaround by changing the steps in the workflow .yaml file.

Kill all processes first using pm2 kill before running npm ci and npm run build.

Example:

steps:
  - uses: actions/checkout@v3
  - name: Use Node.js ${{ matrix.node-version }}
     uses: actions/setup-node@v3
        with:
          node-version: ${{ matrix.node-version }}
          cache: "npm"
  - name: Kill App via pm2 kill
    run: sudo pm2 kill <--- DO THIS
  - run: npm ci
  - run: npm run build
  - name: Setup .env
    run: echo "${{ secrets.PROD_ENV }}" > .env
  - name: Start the App
    run:  sudo pm2 start npm -- start
   # NOT WORKING 1
    run: sudo pm2 restart npm -- start
   # NOT WORKING 2
    run: |
      sudo pm2 kill
      sudo pm2 start npm -- start

[duchicong]

You can read more at: https://nextjs.org/docs/app/api-reference/next-config-js/generateBuildId
run build. It will generate a build ID and then run start to resolve the issue.

[mohamed1408]

This worked for me:

1. npm run build
2. npm start

Note: If npm run build uses pnpm. Install pnpm before running npm run build

Install PNPM:

1. Open Windows Power Shell as Administrator
2. run command iwr https://get.pnpm.io/install.ps1 -useb | iex

[eduvnsm]

That worked for me too thx

[mohamed1408]

Nice!

[LizethVictoria20]

This worked for me, thanks.

[tamvo22]

I had the exact same problem with missing \\.next\\BUILD_ID for my Nx workspace project, which builds outDir to {workspaceRoot}/dist/
I resolved the issue by adding the dirDir option in next.config.js to point it to the right build directory.

// next.config.js
const nextConfig = {
       ...
       distDir: '../../dist/apps/{my-app}/.next',
}

[munim]

Based on generateBuildId documentation, I have added the following in my next.config.js and passed VERSION environment variable during container initiation.

  generateBuildId: async () => {
    // This could be anything, using the latest git hash
    return (process.env.VERSION || Date.now() + Math.round(Math.random() * 2441139)).toString();
  },

[swarnpallav]

@LLytho If you monitor the build log, you will find that the pages are not being generated. The BUILD_ID is generated during the build phase. In my case page generation including BUILD_ID is not getting generated. If you are also facing this and you have found the solution then please help.

[wooseok123]

For me, it was because of setting the output option "export". The BUILD_ID isn't generated in that option. (Idk why)
So i added the scripts named "local" to test the builded version in local. (By the way, i set the 'distdir' option to "./dist")

1. install cross-env

npm i -D cross-env

2. add script

  "scripts": {
      ...
    // The value of the "process.env.NODE_ENV" during next build is "production". 
    // So change the NODE_ENV value by using "cross-env"
    // It didn't affect anything because "build" scipt isn't modified.
    "start": "cross-env NODE_ENV=local next start",
    "local": "cross-env NODE_ENV=local next build"
  },

3. change next.config.js option

const isProduction = process.env.NODE_ENV === 'production';
const nextConfig = {
    ...
    output : isProduction ? "export" : "standalone",
}

[eliezer-alves]

I think I understand what happened, at least to me:

I tried to run the start script without first generating any build, so the .next folder doesn't exist.

Basically:

Do not run the start script without first running the dev or build script.

The .next folder is generated when we run the build script or even the dev script. Therefore, you run npm run dev, or if you run start you have to ensure that the build already exists (running npm run build).

Maybe it will help someone out there.

[flotwig]

This happens when I forget to use next dev and use next start. Could use a better error message here.

[flotwig]

I opened a PR to explore improving this error message: #62404

[flotwig]

PR was merged, this error should be easier to understand now.

[IanAndy]

npm run build

then

npm run start

This worked for me

[SharadJangid]

1. Update Node and Next.js:

   • Ensure you have the latest version of Node.js installed.
   • Update Next.js to the latest version:

     npm install next@latest
     

2. Clean Reinstall Next.js:

   • Uninstall the existing Next.js package:

     npm uninstall next
     

   • Install Next.js again:

     npm install next
     

3. Build and Start:

   • Run the build command:

     npm run build
     

   • Start the production server:

     npm run start
     

4. Check for Errors in VS Code:

   • Open your project in Visual Studio Code (VS Code).
   • Inspect the terminal output for any error messages.

Note:
Make sure to check the official Next.js documentation for more detailed information: https://nextjs.org/docs

Feel free to close this issue if the problem is resolved, or provide additional details for further assistance.

[Roxannej]

Great

[jsuskin]

Idk if anybody else is having the exact issue I was having but it seems like we're all getting the same errors. I'm somewhat new to nextjs. I've worked a lot w plain react in the past and recently I've been working a lot w react native. I got into the habit of using anonymous functions for my component names. Apparently ESLint doesn't like that. I named the components I was exporting a voila, no more errors. After assigning names to those exported functions and successfully running npm run build, npm start and npm run dev both work as expected now. Idk if this will solve everybody's issues but maybe it'll help some of y'all out.

edit: this worked for a day but then i ran into the same issue the next day (did not install any packages in that time so idk). did these steps again and that fixed the issue for now but im anticipating running into it again. sry guys

[liyf0520]

I looked at the repair method mentioned above and tried to build it first. It can work normally after starting. This is useful to me. I used node:21.7.1 next:14

[Dexdot]

• In next.config.js set output: 'standalone'
• When you want to start app use node .next/standalone/server.js instead of yarn start

That helped me to fix this.

https://nextjs.org/docs/pages/api-reference/next-config-js/output
https://github.com/vercel/next.js/blob/canary/examples/with-docker

[mosrahmani]

to solve this issue you should initialize the folders with npm run build then serve the app with npm run start, this worked for me ✨

[flacial]

After starting the dev server with next dev, next start will throw the same error. I'm assuming next dev modifies the .next folder in a way that erases whatever next start depends on. As a sane developer, I'd imagine these two commands are very unrelated to one another.