Unable to run package.json scripts using yarn
See original GitHub issue- Maizzle Version: 4.0.0
- Node.js Version: 16.5.3
Hi,
As of maizzle 4.0.0 there’s a problem executing package.json scripts that use the maizzle
command, IF you’re using yarn
instead of npm
:
yarn run v1.22.10
$ maizzle build production
env: node\r: No such file or directory
error Command failed with exit code 127.
To reproduce:
- Create a new starter project:
maizzle new
- Delete
package-lock.json
and runyarn install
- Run
yarn dev
oryarn build
Thanks!
Issue Analytics
- State:
- Created a year ago
- Reactions:3
- Comments:30 (14 by maintainers)
Top Results From Across the Web
yarn can't run scripts in package.json · Issue #1045 - GitHub
When I try yarn , I use command yarn run dev or yarn start , it's not working. Some message error: yarn run...
Read more >Why won't Yarn run scripts from the package.json?
Update your yarn package with npm or reinstall using brew. I'm using nvm for npm/node and I had the same problem with v0.15.1....
Read more >Fix Unable to Run Yarn in Windows Terminal - PowerShell
To fix it, open PowerShell as administrator, again make sure to run this in PowerShell, not with the regular command prompt (cmd). Copy...
Read more >Run yarn/npm scripts with fzf | sancho.dev
In a Node enviroment or a project with a package.json, It's very common to have a field "scripts" inside the package.json which stores...
Read more >package.json - Yarn
Scripts are a great way of automating tasks related to your package, such as simple build processes or development tools. Using the "scripts"...
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 FreeTop 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
Top GitHub Comments
Hmm no other ideas for now, except to blame yarn 🙈
Need to check this with more users to ensure it’s not some strange edge case and find out what’s causing it…
Can confirm the issue, my reproduction flow:
maizzle
wasn’t installed globallynpm
.yarn
, errors start occurring when runningnpm run dev
.yarn.lock
and runnpm install
.node_modules
and reinstalling withnpm install
.Versions: