Error on fresh `start`

[mfranzke]

Which generators are impacted?

• All
• HTML
• React
• Angular
• Vue
• Web components
• Power Apps

Reproduction case

If you start up with e.g. the command npm run clean && npm i && npm run build && npm run start the following error appears:

> patternhub@0.1.0 next:start
> next start

   ▲ Next.js 14.1.4
   - Local:        http://localhost:3000

[Error: ENOENT: no such file or directory, open '…/showcases/patternhub/.next/BUILD_ID'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '…/showcases/patternhub/.next/BUILD_ID'
}
npm ERR! Lifecycle script `next:start` failed with error: 
npm ERR! Error: command failed 
npm ERR!   in workspace: patternhub@0.1.0 
npm ERR!   at location: …/showcases/patternhub 
ERROR: "next:start" exited with 1.
npm ERR! Lifecycle script `start` failed with error: 
npm ERR! Error: command failed 
npm ERR!   in workspace: patternhub@0.1.0 
npm ERR!   at location: …/showcases/patternhub

Expected Behaviour

No error would come up at starting our system.

Screenshots

No response

Browser version

None

Add any other context about the problem here.

To my impression this is related to that the patternhub build wouldn't be done in advance within the start script process.

[nmerget]

npm run clean removes some files in patternhub, there is an issue with git clean -dfx --exclude=.env

[mfranzke]

npm run clean removes some files in patternhub, there is an issue with git clean -dfx --exclude=.env

If it would remove too many files, this might in a state (or at least nearly) like a fresh git cloned repository to your localhost. Afterwards it's the commands listed within our getting started. So if these aren't enough, we still need to include more information in there, isn't it?

[mfranzke]

@nmerget even when getting a fresh clone / download of this repo, running npm i && npm run build && npm run start afterwards produces (other) errors. We should look into this.