-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enoent undefined ls-remote -h #9
Comments
Hi... 2022-04-10T09:42:36.007Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected] any Ideas, clue ? |
should be reladted to this issue solved by version 1.4.8 |
unfortunately not, see the log above "2022-04-10T09:42:36.007Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict node-red-google-notify@1.4.8" |
can please give some more details about the host computer, do you use node-red as standanlone or as home assistant add-on ? |
(sorry for the delay).. sure... |
Hello , I am attempting to install - node-red-google-notify
The installation fails and I am getting the following error in the log file :
29 verbose Linux 5.11.22-4-pve 30 verbose argv "/usr/bin/node" "/usr/bin/npm" "install" "node-red-google-notify" 31 verbose node v14.18.1 32 verbose npm v6.14.15 33 error code ENOENT 34 error syscall spawn git 35 error path git 36 error errno -2 37 error enoent Error while executing: 37 error enoent undefined ls-remote -h -t git://github.com/orcema/file-server.git 37 error enoent 37 error enoent 37 error enoent spawn git ENOENT 38 error enoent This is related to npm not being able to find a file. 39 verbose exit [ -2, true ]
Is there something else I can try?
The text was updated successfully, but these errors were encountered: