NPM 5.7 recursively changing ownership of system directories when using sudo npm -g
-
@thecpuwizard said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
@jaloopa said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
@cabbage said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
Hmm. Maybe I'll pop open a pull request to fix this in the npm docs. Oh, wait; somebody already did: https://github.com/npm/docs/pull/679. It hasn't been merged in the two years since it was opened, though, or even acknowledged by a member of the npm team, because FYTW.
It's open source you can fix it yourself stop complaining etc.
Open Source does NOT mean that "just anybody" can make changes to the repository.....
Pull Requests Accepted! Possibly!
-
@ben_lubar said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
@gleemonk I want a
docker
-like desktop OS where I can run every program in its own virtual filesystem and process space.I could have sworn someone was doing that, but for the life of me I can't find it again...
-
@lorne-kates said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
@gąska said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
Your boring ass is another man's treasure.
This is Chad.
He isn't much for clubs or discos or loud, trendy restaurants. He loves nothing more than what others would call a "boring" night in; some takeout, some video games, maybe a movie. All relaxed. Maybe he isn't a party animal, but he'll cherish you like a treasure. Every part of you.
Even your boring ass.
Hey! My hair doesn't look like that at all!
-
@ben_lubar said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
@jazzyjosh said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
@izzion No, 5.7.0 and 5.7.1 are both marked as pre-releases.
Under the SemVer spec, which NPM claims to use, 5.7.0 and 5.7.1 are very much not pre-release version numbers.
And does SemVer even HAVE pre-release version numbers? I don't actually think so.
Nor is it actually its purpose. The point of SemVer is to indicate how compatible or not is the interface of the new version. That, however, means, that the package managers should have some additional indicator of that. Something like “release channel”. Alas, they generally don't.
-
@bulb said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
And does SemVer even HAVE pre-release version numbers? I don't actually think so.
A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version.
When major, minor, and patch are equal, a pre-release version has lower precedence than a normal version.
-
@pjh said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version.
That's for the development snapshots. I don't think you can upload those in the npm repository at all.
Anyway, I was thinking about the “release channels” a lot of software has. You release 1.3.8 to beta, then 1.3.9 to beta, then promote 1.2.19 to stable, because you are satisfied with it, etc.
And the npm repository even seems to have that—since
npm install
won't install the “next”. The issue really is that the distinction betweeninstall
andupgrade
is totally opaque and counter-intuitive. Both should use the “stable” version unless given an option.
-
@bulb said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
That's for the development snapshots. I don't think you can upload those in the npm repository at all.
You're now complaining about npm. The complaint I was answering related to SemVer.
-
@bulb said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
Anyway, I was thinking about the “release channels” a lot of software has.
You'd do them by telling your package manager that you're happy to accept certain non-final versions as well (e.g., “I'm on the
beta
channel”, meaning that1.3.8-beta-1
and1.3.8-beta-2
are considered upgrades to1.3.7
but are still downgrades from1.3.8
). Yes, this does mean that the release process has to update the version identifier in the artefact; if you can't do that reliably, you are really not in a good state to make any sort of release at all.
-
@bulb said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
Anyway, I was thinking about the “release channels” a lot of software has. You release 1.3.8 to beta, then 1.3.9 to beta, then promote 1.2.19 to stable, because you are satisfied with it, etc.
Node has "LTS" and "stable" channels. This was a screwup on stable. I always use LTS, exactly because of shit like this.
-
@ben_lubar said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
@erufael said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
@boomzilla It was rated by the Elves, and they think the human race is still too young for it.
Those human scholars are pretty ancient too.
-
Dem fukken hipsters, all of them
One hipster shit releases a NPM that fucks your system, because YOLO.
A few dozen of other hipster shits start whining because they fukken
sudo npm upgrade -g
as a part of release workflow, no less, and they fuck up production.The original hipster shit starts “you’re holding it wrong” argument, when he should be like “ohshit ohshit I apologize and unpublish my shit right now.” A philosophical debate on software versioning starts, wherein abovesaid hipster shit defends its fuckup, because a spec says prerelease versions MAY go untagged. Listen shit, just because you CAN lick your balls, presuming you have even got them, it doesn’t mean you should do that in public.
Fuck deez damn hipsters, that whole wannabee devops community is rotten.
-
@wft said in NPM 5.7 recursively changing ownership of system directories when using sudo npm -g:
Fuck deez damn hipsters, that whole wannabee devops community is rotten.
That's 'cause "wtfcorp too cheap to hire both sysadmins and developers and instead hires for a position called IT" is so 2001...