Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
package.json file missing when running npm run start
See original GitHub issueWhen I run npm run start with a fresh install I get an error saying
npm ERR! code ENOENT
npm ERR! errno -4058
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open 'XXXXX\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (3 by maintainers)
Top Results From Across the Web
npm can't find package.json - Stack Overflow
if the package.json file is already created in the project directory then there is a possibility that you are not running your project...
Read more >npm ERR! Missing script: "start" [Solved] | bobbyhadz
First, make sure your package.json file has a start command in the scripts object. package.json.
Read more >[Solved] npm err! missing script: start - ItsJavaScript
The npm err! missing script: start mainly occurs if you have not specified the entry path in package.json to run the application. We...
Read more >npm ERR! Missing script: "start" (How to Fix!) - Stack Diary
The "npm ERR! Missing script: 'start'" error is a common error that occurs when you try to run the npm start command on...
Read more >How to fix npm ERR! missing script: start issue
The npm error missing script: “start” means that npm can't execute the “start” script from your package.json file.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@alexiskattan Did you first
cdinto theclientfolder?Without using -v commands, the container starts without any issue.
$ docker run -it -p 3000:3000 fcd702193970 //success