samyk / easel-driver

Easel driver for Linux, Mac, Windows, ARM, Raspberry Pi, Intel, FTDI, CH340, CH341, CP210x, FTDI clones, local, and remote access to GRBL-based CNC controllers
95 stars 24 forks source link

Driver Fails to Install - nvm is not compatible with the npm config "prefix" option: currently set to "" #28

Closed Philldapill85 closed 2 weeks ago

Philldapill85 commented 3 weeks ago

Not sure what the issue is. I had the Easel driver successfully installed in my old Pi 2B, but the OS was insanely slow, so I upgraded to a Pi 4B. New OS install (Bullseye as well as Bookworm) and the driver doesn't work on these. Looks like something has changed that has broken the install. Here's the output:

Philldapill@raspberrypi:~ $ curl https://raw.githubusercontent.com/samyk/easel-driver/master/easel-driver.sh | sh -x % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 65 63+ [ -e46 easel-driver ] 0 0 --:--:-- --:--:-- --:--:-- 0 65 4125 0 0 11178 0+ --date +%s 100 6346 100 6346 0 0 17105 0 --:--:-- --:--:-- --:--:-- 17105

=> nvm source string already in /home/Philldapill/.bashrc => bash_completion source string already in /home/Philldapill/.bashrc /usr/bin/env: ‘node’: No such file or directory nvm is not compatible with the npm config "prefix" option: currently set to "" Run nvm use --delete-prefix v18.20.4 --silent to unset it. => Close and reopen your terminal to start using nvm or run the following to use it now:

export NVM_DIR="$HOME/.config/nvm" [ -s "$NVM_DIR/nvm.sh" ] && . "$NVM_DIR/nvm.sh" # This loads nvm [ -s "$NVM_DIR/bash_completion" ] && . "$NVM_DIR/bash_completion" # This loads nvm bash_completion

Done! Easel driver running in background. Run screen -r to bring it to foreground. Philldapill@raspberrypi:~ $

samyk commented 2 weeks ago

Looks like the node or nvm piece either didn't install or activate properly...don't have a moment to look at this right now but happy to accept PRs.

Did you already have nvm/node installed? If so, maybe there was a conflict or an update to support a pre-existing install would be nice. This is in your logs:

=> nvm is already installed in /home/Philldapill/.config/nvm, trying to update using git
=> => Compressing and cleaning up git repository
=> nvm source string already in /home/Philldapill/.bashrc
=> bash_completion source string already in /home/Philldapill/.bashrc
/usr/bin/env: ‘node’: No such file or directory
nvm is not compatible with the npm config "prefix" option: currently set to ""
Run nvm use --delete-prefix v18.20.4 --silent to unset it.
=> Close and reopen your terminal to start using nvm or run the following to use it now:
Philldapill85 commented 2 weeks ago

This was a fresh install of the latest Raspbian as of 10/22/24. Not sure why, but a fresh install of nvm/node fixed it for some reason.

I don't know how you accomplish what you do in 24 hour days, but it's appreciated immensely!