rsnext/errors/production-start-no-build-id.md
Tim Neutkens c792317295
Clear up production build missing message for next start and next export (#19777)
Adds an err.sh link to the production build missing message. Also clears up `valid` as `production`.

Also fixes an edge case where an unhelpful error would be thrown because we checked for `.next` instead of `.next/BUILD_ID`

Added the out directory location as the list line during export to make sure people know where the files are output. 

Fixes #19778
Fixes #19788
2020-12-08 15:16:56 +00:00

10 lines
359 B
Markdown

# Could not find a production build
#### Why This Error Occurred
When running `next start` or a custom server in production mode a production build is needed.
#### Possible Ways to Fix It
- Run `next build` to create a production build before booting up the production server.
- If your intention was to run the development server run `next dev` instead.