Upgrade from 22.5.1 to 22.6.0 fails with error `/bin/sh: 1: babel: not found`
See original GitHub issueAfter upgrading to 22.6.0, we get the following build error when installing eslint-plugin-jest:
error /root/project/bootstrap-vue/node_modules/eslint-plugin-jest: Command failed.
Exit code: 1
Command: yarn build
Arguments:
Directory: /root/project/bootstrap-vue/node_modules/eslint-plugin-jest
Output:
yarn run v1.13.0
$ babel --extensions .js,.ts src --out-dir lib
/bin/sh: 1: babel: not found
error Command failed with exit code 127.
Fails due to the postinstall
command introduced via #257 which tries to compile files with babel.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:14
- Comments:11 (5 by maintainers)
Top Results From Across the Web
npm - Babel command not found - Stack Overflow
First, you need a package.json file. Telling npm to install without one will throw the npm WARN enoent ENOENT: no such file or...
Read more >babel: command not found error [Solved] | bobbyhadz
Use npx to solve the error "babel: command not found", e.g. npx --package @babel/cli babel --version or install the package globally by running...
Read more >Upgrade to Babel 7
In Babel 7, values are resolved consistently either relative to the config file that loaded them, or relative to the working directory. Assuming...
Read more >[Solved] react-scripts: command not found - ItsJavaScript
The react-scripts: command not found error mainly occurs if the dependencies are not installed or if the react-scripts is not installed.
Read more >Deployment failure: babel command not found - Support
Deployment fails and it says babel command not found. ... Kameshwaran March 12, 2020, 11:40am #1. Deployment fails and it says babel command...
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
🎉 This issue has been resolved in version 22.6.1 🎉
The release is available on:
Your semantic-release bot 📦🚀
I am getting a similar issue, but in my case it’s
yarn
that is not installed, notbabel
. So it fails earlier.