ChanceHarrison
ChanceHarrison
Potentially related to https://github.com/beemdevelopment/Aegis/issues/842?
I believe I have encountered this issue, and I believe I may be able to provide some insight. # Hypothesis There is a bug in (relating to?) the local relay...
@rossengeorgiev Are you open to contributions pertaining to this issue?
This is not a Jubilinix-specific issue. It occurs on Raspbian too. Actually, I can't think of any installation that _wouldn't_ run into this issue. Calling `sudo npm install npm@latest` installs...
I am interested as to why you would not be seeing the issue too. My hypothesis is that the special-case logic that exists currently for [handling Jubilinux nodejs install via...
@scottleibrand Thanks for sharing. Are you able to speak to the last part of my previous comment? > I'd be especially interested in what the output of this line running...
@scottleibrand Appending `--dry-run` will give the output without making any changes.
For example, when I run that command on my Pi rig: ``` # npm install npm@latest -g --dry-run + [email protected] added 71 packages from 26 contributors, removed 292 packages and...
@scottleibrand I believe there has been a misunderstanding. `sudo npm install npm@latest -g` is _not_ the workaround; it is the flawed line that exists in the scripts currently. A line...
@scottleibrand Once npm is in that state, no npm command (that I know of) will fix it. You will have to reinstall npm manually, update to a sufficiently new version...