NPM package that does nothing accidentally removed, breaks shit AGAIN
-
@Tsaukpaetra said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
its'
That's a new one. :D
-
@asdf said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@Tsaukpaetra said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
its'
That's a new one. :D
Yeah, it's a legacy issue with my grammar systems. I don't have the ability to correct it myself, so I just have a Censor rule that tries to go back and correct those when possible. Seems I missed that one.
-
@Tsaukpaetra In my head, this was your original thought process: "It's? Or its? Ah, fuck it, let's just use its' and confuse everyone!"
-
@asdf said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@Tsaukpaetra In my head, this was your original thought process: "It's? Or its? Ah, fuck it, let's just use its' and confuse everyone!"
I'm not that sadistic.
No, it's supposed to be the possessive of "it", but since "it" is a reference to an object, it doesn't get de-referenced properly in the rules (i.e. gets treated like a name, for example), despite the rule saying it should be just "its" and so it gets the ' tacked on.
-
@Tsaukpaetra don't worry it confused me and I am a native English speaker.
-
@lucas1 said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
My question would be, what happens with stuff like Nuget if that is part of your build process? I don't think this is something that is unique to NPM.
NuGet has a local package cache, so you might be okay until you try to upgrade the package (or move to a new build server). Worst-case, you drop the .nupkg file from a dev's machine on a network share somewhere, and add that as an additional repository in your NuGet.config file.
-
@DogsB said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
I think I traced why its usage is everywhere
First example on this page https://nodejs.org/api/https.html
No it's a built-in module.
require
ing it is fine.npm install
ing it is not.
-
@cark said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
ball-whacking
-
@cvi said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@dkf said in [NPM package that does nothing accidentally removed, breaks shit AGAIN]
That's stable. With lots of in it.
Physics has a term for it: meta- stable. It's sort of stable, unless you start poking it, or just happen to glance into its general direction.
meta
-stable means: depending on the observer it could be stable or stable full of ! That explains all the drama wtd had with overmeta
.d
-
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
back in the pre node 0.10 days
That's from v0.1.31.
-
@Polygeekery You dare suggest the possibility of interpreting my words in a dirty way?! That's a ballsy move
-
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
back in the pre node 0.10 days
That's from v0.1.31.
So very very very long time ago. Got it.
-
@masonwheeler said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
Again, this would not happen if NPM used a proper relational database to track packages and dependencies. It would be literally impossible to delete a package where other packages exist that depend on it.
I failed to properly follow our written internal process for checking if an unpublish is safe.
...which is precisely why it should be done with referential integrity rather than a checklist that a fallible human has to follow. This is already a solved problem, but people too trendy to use SQL keep screwing it up.
Don't delude yourself: a relational database would greatly help matters but it wouldn't 100% solve the problem. The scale of the web means that there are hundreds of projects depending on high-level libraries, most of those projects will never be recorded in the dependency database.
The only way to be sure is to never unpublish anything, give everything a version (even if its just a straight counter) and to avoid name collisions by using a nearly-globally-unique thing like a (sub-)domain name as a namespace qualifier.
-
The other way to solve this is to have the package repository maintainers disallow packages that are 1) duplicates and 2) clusterfucking retarded.
There is no way a central package repository should allow shit like the isBetween stuff getting in in the first place, and for cases like fs, it should be removed and a warning added so people fix their dependency chains.
-
@Arantor It's tempting to start a curated repository but it will definitely run into a lack of curators because it just isn't webscale.
I've seen it with the Sonatype Maven repository, at first they had real reviewers but later it became more of a rubber stamping service. They'd check that all required metadata is present without checking if it makes sense to have umpteen different dependencies for your
fart
library.
-
@JBert I'm not even talking about validation of dependencies.
Just an initial sanity check: does the library, on first submission, do something so fucknuts retarded as expose a function call and all associated boilerplate for
x > y
orif x >= y && x <= z
stuff. Just keep the lowest denomination of shit out as a first step.
-
@Arantor "If it has less than 20 SLOC it is rejected".
-
@Arantor said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@JBert I'm not even talking about validation of dependencies.
Just an initial sanity check: does the library, on first submission, do something so fucknuts retarded as expose a function call and all associated boilerplate for
x > y
orif x >= y && x <= z
stuff. Just keep the lowest denomination of shit out as a first step.Okay, so you really want to decimate the NPM repository...
-
@JBert you make it sound like a bad thing!
-
@Jaloopa said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@bb36e said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@ben_lubar go would also not have this issue because not enough people use it for the issue to be discovered
Crucial Go package removed. Breaks both other Go packages
That's a different problem. The problem I'm talking about is someone releasing a package with the same import path as a standard library package and people downloading the wrong one.
-
@JBert said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@Arantor said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@JBert I'm not even talking about validation of dependencies.
Just an initial sanity check: does the library, on first submission, do something so fucknuts retarded as expose a function call and all associated boilerplate for
x > y
orif x >= y && x <= z
stuff. Just keep the lowest denomination of shit out as a first step.Okay, so you really want to decimate the NPM repository...
decimate would only remove one in ten.... we would need to apply the decimation 21 times to get rid of all the really crap stuff.
that might be a bit harsh, but think how much better the world will be then!
-
Mommy! Timmy broke the world again!
-
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@JBert said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@Arantor said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@JBert I'm not even talking about validation of dependencies.
Just an initial sanity check: does the library, on first submission, do something so fucknuts retarded as expose a function call and all associated boilerplate for
x > y
orif x >= y && x <= z
stuff. Just keep the lowest denomination of shit out as a first step.Okay, so you really want to decimate the NPM repository...
decimate would only remove one in ten.... we would need to apply the decimation 21 times to get rid of all the really crap stuff.
that might be a bit harsh, but think how much better the world will be then!
I was not aware there were a sextillion packages on npm.
-
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
decimate would only remove one in ten.... we would need to apply the decimation 21 times to get rid of all the really crap stuff.
Sounds about right. Except I think that you'll need 42 times; my impression of the general quality of npm packages isn't the highest.Hmmโฆ let's work that out.
Decimation is โremovalโ of one in 10, i.e., 10%, leaving 90% behind (= 0.9).
0.910 โ 0.1
So we have (about) 10% left after 21 decimations.
-
@dkf I thought decimation was reduction to 10%, not by 10%.
-
-
@ben_lubar It could be either; the term originally referred to the 'eliminate one in ten' form, and was one of the punishments given to disloyal troops in the Roman army. The 'spare one in ten' form came later, and probably originated when the term was used ironically to describe their crushing defeat at Teutobergwald in 9 AD, in which only about 70 men out of the three legions (at least 20,000 legionnaires, 300 cavalry, and 3000 non-Roman auxiliaries) survived.
-
@HardwareGeek said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
"i am fs"
"I am not the package you're looking for."
"fs has been a core package since node 0.10 and there is no need to npm install this version"
-
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@dkf I thought decimation was reduction to 10%, not by 10%.
most people do. they are wrong. :-P
-
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@dkf I thought decimation was reduction to 10%, not by 10%.
most people do. they are wrong. :-P
If most people think something about the definition of a word, doesn't that make them correct?
-
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@dkf I thought decimation was reduction to 10%, not by 10%.
most people do. they are wrong. :-P
If most people think something about the definition of a word, doesn't that make them correct?
if enough people do that the OED changes the definition, then yes. the OED has not updated the definition so they are wrong.
-
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@dkf I thought decimation was reduction to 10%, not by 10%.
most people do. they are wrong. :-P
If most people think something about the definition of a word, doesn't that make them correct?
if enough people do that the OED changes the definition, then yes. the OED has not updated the definition so they are wrong.
Kill, destroy, or remove a large percentage or part of
-
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@dkf I thought decimation was reduction to 10%, not by 10%.
most people do. they are wrong. :-P
If most people think something about the definition of a word, doesn't that make them correct?
if enough people do that the OED changes the definition, then yes. the OED has not updated the definition so they are wrong.
Kill, destroy, or remove a large percentage or part of
yes. you'll note that the definition does NOT say "to kill 9 in 10" even the common one just says "kill a bunch of things"
so that doesn't defend your position, and improves mine. :-P
-
@accalia OED says "a large percentage", which means the modern usage of decimate has nothing to do with the number 10.
-
@accalia DESCRIPTIVISM VS PRESCRIPTIVISM: WHO IS RIGHT??
descriptivists, obviously
-
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@accalia OED says "a large percentage", which means the modern usage of decimate has nothing to do with the number 10.
be that as it may, it doesn't mean 9 in 10, which is what you thought it meant.
-
@bb36e said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@accalia DESCRIPTIVISM VS PRESCRIPTIVISM: WHO IS RIGHT??
When s wage war, the only winner is
deathilliteracy.
-
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@accalia OED says "a large percentage", which means the modern usage of decimate has nothing to do with the number 10.
be that as it may, it doesn't mean 9 in 10, which is what you thought it meant.
You know, it's possible for two people to be wrong about the same thing.
-
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@accalia said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@ben_lubar said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
@accalia OED says "a large percentage", which means the modern usage of decimate has nothing to do with the number 10.
be that as it may, it doesn't mean 9 in 10, which is what you thought it meant.
You know, it's possible for two people to be wrong about the same thing.
my definition's actually listed.
so nya! :-P
-
@Arantor said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
The other way to solve this is to have the package repository maintainers disallow packages that are 1) duplicates and 2) clusterfucking retarded.
Maybe they can switch it with an alias, that warns in big red fonts that this package is obsolete. Done, solved
-
@dse that only remediates the fs case, it doesn't fix the isBetween case.
-
@Arantor The isBetween case solves itself: let people break it, it's stupid to be using it and you should feel bad anyway.
-
@Yamikuronue its mere existence is proof that natural selection doesn't entirely apply, that some people lack the critical thinking and introspection to not use it and so we need to apply the cluebat occasionally.
-
people like to put github profiles on their resumes. It'll even out.
"We had a look at your github account and had a few concerns. Can you explain this dependency list to us?"
-
@Yamikuronue said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
people like to put github profiles on their resumes. It'll even out.
"We had a look at your github account and had a few concerns. Can you explain this dependency list to us?"
Yeah I definitely see that happening at 95% of shops.
-
@Yamikuronue said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
"We had a look at your github account and had a few concerns.
Can you explain this dependency list to us?Can you explain how to handle where there are two developers working together on the same codebase? We can't figure out how to do it without locking everything."FTFY. There's a lot of nincompoops out there.
-
@dkf I've had companies not even manage to spell GitHub correctly. Or BitBucket for that matter.
-
@Arantor said in NPM package that does nothing accidentally removed, breaks shit AGAIN:
BitBucket
ButtBicket?
-
@Luhmann oddly enough, no.
But I have seen BucketBit, Bitbuck, BitlyBuck... and I just have to wonder... are you people trolling or really clueless?
Also, I've frequently seen 'Git' when they mean 'GitHub'.
-
@Arantor No BitHub or GitBucket? I am disappoint.