Can not run "next start"

[khrome83]

Even though I run "next build", I am not able to run "next start".

I can confirm that a .next folder is created, but I get the following error -

"Could not find a valid build in the '.next' directory! Try building your app with 'next build' before starting the server."

[khrome83]

Uses "next": "^2.0.0-beta.22"

[timneutkens]

Can you check if your .next folder has a BUILD_IDfile?

[timneutkens]

Also, can you provide a sample repository?

[khrome83]

Where is the BUILD_ID at?

I won't be able to standup a sample repo currently. Here is a screenshot of the output.

[timneutkens]

@khrome83 It's located right inside .next (.next/BUILD_ID). From the looks of it this .next folder is from a next dev build. Which is strange because next build should remove the .next folder and then create a new one with the production build. Can you try manually removing .next and running next build again?

[khrome83]

Apparently it is not building a .next folder. I deleted the .next folder and confirmed that it was because of dev.

When I run npm build which in turn runs next build it just ends. It does not give me any output.

When I run ./node_modules/.bin/next build then it does produce a production .next folder with a BUILD_ID inside.

This is not a issue only locally on my machine. I can confirm, that on node 6.9.1 this is also happening on the GitLab-CI environment.

[nkzawa]

@khrome83 try npm run build instead of npm build.

[khrome83]

Ok that works locally. It's strange because npm build does not trigger unknown NPM command, and does not trigger unknown script error

[nkzawa]

Because it's a known command 😂 😂 😂

https://docs.npmjs.com/cli/build

This is really confusing. Anyway closing now.