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.
Errors when running `yarn start`
See original GitHub issueAfter following the install instructions, I get the following when running yard start
Issue Analytics
- State:
- Created 5 years ago
- Comments:14
Top Results From Across the Web
Error: yarn start - error Command "start" not found
this error happens when you're running yarn start in a wrong directory instead of the root directory where package.json is. if they didn't...
Read more >Error Codes | Yarn - Package Manager
A list of Yarn's error codes with detailed explanations. ... Running yarn install will almost certainly fix this particular error.
Read more >`yarn start` fails with error message · Issue #1155 - GitHub
The underlying issue was that the yarn path was set incorrectly. If you have this error then you will see a yarn-error.log file...
Read more >Yarn Start not working : r/react - Reddit
When I run yarn start I would get: warning package.json: No license field error Command "start" not found.
Read more >Getting error messages when running yarn commands
One diagnosing hack would be to manually add the package to your root package.json . So try yarn add -W @ardatan/aggregate-error ( -W...
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
You have to remove yarn.lock file then run yarn. I had the same issue before I removed yarn.lock
@frostyweather @jpeterson just had the same issue.
Recreates issue above gatsby-style-guide-guide git/master ❯ node -v = v10.3.0 ❯ npm -v = 6.1.0
Works gatsby-style-guide-guide git/master* ❯ node -v = v8.11.2 ❯ npm -v = 5.6.0
I haven’t been able to figure out what is/are the offending issues though
UPDATE: Little more info. I ran
yarn upgrade-interactiveon the repo in v10.3.0, I selected all outdated modules to be updated, went through the process and after updating the process ofyarnthenyarn startworks as expected.I haven’t yet pinpointed exactly which package is the culprit.