Yarn run start broken in last version
See original GitHub issuePrerequisites
- Using yarn
- Using an up-to-date master branch
- Using latest version of devtools. See wiki for howto update
- Link to stacktrace in a Gist (for bugs)
- For issue in production release, devtools output of
DEBUG_PROD=true yarn build && yarn start
Expected Behavior
yarn run start should run the application in production mode without packaging it
Current Behavior
electron can’t read import instruction in index.js
Possible Solution
Maybe add some transpiling before ?
Steps to Reproduce (for bugs)
1.yarn run start or yarn start
- 💔
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Error: yarn start - error Command "start" not found
I got the same error message "start" command not found. ... create-react-app version). -Then run the command yarn start and it will work....
Read more >Error Codes | Yarn - Package Manager
A list of Yarn's error codes with detailed explanations. ... a dependencies field without running yarn install , or because you added a...
Read more >Common errors | npm Docs
Broken npm installation; Random errors; No compatible version found; Permissions errors ... npm not running the latest version on a Windows machine ...
Read more >npm, pnpm, and Yarn | WebStorm Documentation - JetBrains
WebStorm also lets you run and debug npm, Yarn, and pnpm scripts. ... Ctrl+Space or start typing a version different from the latest...
Read more >Troubleshooting | React Navigation
Sometimes it might even be due to a corrupt installation. If clearing cache didn't work, try deleting your node_modules folder and run npm...
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
start script should be changed to
"start": "cross-env NODE_ENV=production electron ./app/main.prod.js",
the fix work! Thanks @amilajack