-
-
Notifications
You must be signed in to change notification settings - Fork 267
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
Local package.json exists, but node_modules missing, did you mean to install? #147
Comments
Not that anyone is even looking at this but here is the complete log: |
from the logs it looks like you have to run 'npm install' before running the application. |
Thanks, that would probably work but this version of Ubuntu is so stripped down to keep the cost free it wouldn't install npm. |
I also run Nightscout on Google Cloud but get a slightly different error
Or is this the same problem? |
Ended up deploying this as a stand alone service in northflank. Seems to be working fine uploading to my Google Nightscout |
I've setup the NightScout in Google, https://navid200.github.io/xDrip/docs/Nightscout/GoogleCloud.html, and it works so I tried to install this and get this error. Maybe the setup from here doesn't support this?
Here's what I see when I run my start.sh
mstry9@instance-20240511-203125:~/main/nightscout-librelink-up-main$ sudo bash start.sh
start.sh: line 2: rt: command not found
npx: installed 17 in 2.185s
Cannot find module 'typescript'
Require stack:
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] start:
npx ts-node --transpile-only src/index.ts
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm WARN Local package.json exists, but node_modules missing, did you mean to install?
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2024-06-15T00_12_23_032Z-debug.log
mstry9@instance-20240511-203125:~/main/nightscout-librelink-up-main$
The text was updated successfully, but these errors were encountered: