Scott Leibrand
Scott Leibrand
What OS did you see this problem on? Jubilinux? Raspbian?
The reason I asked about the OS is that I haven’t had the same problem flashing and installing fresh rigs with jubilinux. So I assumed it was a Raspbian-specific issue....
My currently running rigs all show: ``` # node -v; npm -v v8.17.0 6.13.4 ``` uname -a shows `3.10.98-jubilinux-edison #3 SMP PREEMPT Sun Aug 13 04:22:45 EDT 2017 i686 GNU/Linux`...
I didn’t run that because I didn’t want to change anything on my working rigs. Is there a read-only command to get the info you’re looking for?
``` # sudo npm install npm@latest -g --dry-run npm WARN notsup Unsupported engine for [email protected]: wanted: {"node":"^12.13.0 || ^14.15.0 || >=16"} (current: {"node":"8.17.0","npm":"6.13.4"}) npm WARN notsup Not compatible with your...
I finally have to flash and install a new rig, and ran into this problem. Apparently the node/npm maintainers deprecated something since my last install. When I try to run...
That doesn't work either: ``` root@edison-eb5 ~ # sudo npm upgrade -g npm ERROR: npm is known not to run on Node.js v8.17.0 You'll need to upgrade to a newer...
No, this hasn’t gotten much interest yet.
Agreed. Are you volunteering to work on that? 😃
https://github.com/openaps/openaps/compare/master...sulkaharo:wip/nogit?expand=1 "Also supports creating a new openaps instance with git disabled" `openaps init myopenapsinstance --nogit`