Using old node version
See original GitHub issueDescribe the bug
I can’t commit anything when using Husky. It works fine running cmd in terminal. I’m getting the error message
Commit failed - exit code 1 received, with output: 'Husky requires Node 8.6.0, can't run Git hook.'
Version & OS
Github Desktop 2.2.4 MacOS Mojave 10.14.6
Screenshots
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (4 by maintainers)
Top Results From Across the Web
How to change to an older version of Node.js - Stack Overflow
Windows · 1. Install nvm · 2. Install specific node version using nvm · 3. Make the installed version default · 4. Check...
Read more >How to switch Node.js versions with NVM - LogRocket Blog
In this case, you want to switch back and forth between different Node versions, and the easiest way to do this is using...
Read more >How to Change Node.js Version - Fjolt
To change Node.JS versions, we have to first download the version we want. Make sure you have nvm installed first. If you don't...
Read more >Previous Releases - Node.js
Version Date V8 npm NODE_MODULE_VERSION
Node.js 19.3.0 2022‑12‑14 10.8.168.21 9.2.0 111 Downloads C...
Node.js 19.2.0 2022‑11‑29 10.8.168.20 8.19.3 111 Downloads C...
Node.js 19.1.0 2022‑11‑14 10.7.193.20 8.19.3...
Read more >How to install the previous version of node.js and npm
In windows: npm install -g node@version. Example: npm install -g node@10.9.0 · In linux: sudo apt-get install nodejs=version-1chl1~precise1.
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
I ran into a similar issue with GitHub Desktop using node 11.15.0 even though I had already used nvm to
use
LTS (node 14.17.3 at time of writing). I didn’t realize that using thenvm use
command only changes the current environment, not all environments. To fix this, I rannvm alias default 14.17.3
and then restarted GitHub Desktop. That fixed my problem — now GitHub Desktop appears to use that newer nvm default version.This is actually still an issue and not just for the person who reported. Closing it a week later seems a little like telling people to go away.