Live data from Hacker News

Many packages suddenly disappeared

github.com

151–160 of 520 posts

Re: Many packages suddenly disappeared

#151
post #48

Earlier quoted context omitted.

Does "stalinist" work?

Dunno, but it's quite hard to resist childish urges. I note that "jew" is still available, and .jew is a perfectly valid extension which no program has ever claimed. I love all cultures. There's something worth learning from each of them, if you try. But emergent social dynamics are deeply interesting too: I get it (everyone does), and it makes perfect sense. Yet we've all collectively agreed that those are unwholeso…

There‘s a company named „Wix“, which is German for „masturbate“. I really don‘t know why they don‘t use a different name in German speaking countries. Maybe it‘s not a big deal, and people can deal with the fact that words mean different things in different contexts?

Re: Many packages suddenly disappeared

#152
post #71

In my org, we use Artifactory as a cache between us and external sources. They have a free version too. I'd encourage everyone to use it, or something like it. Stop pointing your package managers to the public registry.

What gives you more confidence in them? Just a better track record, or is it a fundamentally more reliable model?

We self-host Artifactory. If our internal instance goes down, it's always possible to fall back to the public registry of language (NPM, Maven, pip etc). It's far more unlikely for our Artifactory and the public registry to go down simultaneously.

Re: Many packages suddenly disappeared

#153
Can anyone explain why the npm registry still exists if it cannot guarantee that uploaded packages remain available? The current state makes it pretty useless as a reliable source te base software on because you never know if you're able to build it again in the future.

They should take a good hard look at NuGet, which does not allow packages to be deleted so builds are guaranteed to be reliable. Still doesn't hurt to locally cache packages with software such as Klondike.

Re: Many packages suddenly disappeared

#154
post #44

Btw. for those who don't know: Yarn (which is an alternative to npm) uses a global cache [1] on your machine which speeds things up, but probably also protects you from immediate problems in cases like the one currently on progress (because you would probably have a local copy of e.g. require-from-string available). [1] https://yarnpkg.com/lang/en/docs/cli/cache/

It's useless in cases like this though, where the package is already invalidated in the yarn cache, which is the case right now for many packages.

You should be using the --frozen-lockfile flag in any production build system.

Re: Many packages suddenly disappeared

#155
post #108

Earlier quoted context omitted.

I just tested, and it definitely looks like a troll / hack. > duplexer3@1.0.1 install /Users/foo/Code/foo/node_modules/duplexer3 > echo "To every thing there is a season, and a time to every purpose under the heaven: A time to be born, and a time to die; a time to plant, and a time to pluck up that which is planted; A time to kill, and a time to heal; a time to break down, and a time to build up; A time to weep, and…

They're referencing the Bible: https://www.biblegateway.com/passage/?search=Ecclesiastes+3&...

The Byrds, Turn! Turn! Turn!

Re: Many packages suddenly disappeared

#156

Earlier quoted context omitted.

They document that they curate package names here: https://www.npmjs.com/policies/conduct I guess lots of people will think that a policy like Avoid using offensive or harassing package names, nicknames, or other identifiers that might detract from a friendly, safe, and welcoming environment for all. stifles their inner something or other though.

seems like a good reflection of the current social climate: they have a policy to prevent mildly offensive package names, and they enforce it, but they don't have a solution to packages randomly disappearing and being replaced with malicious versions.

gotta have priorities.

Re: Many packages suddenly disappeared

#157
post #48

Earlier quoted context omitted.

Does "stalinist" work?

Dunno, but it's quite hard to resist childish urges. I note that "jew" is still available, and .jew is a perfectly valid extension which no program has ever claimed. I love all cultures. There's something worth learning from each of them, if you try. But emergent social dynamics are deeply interesting too: I get it (everyone does), and it makes perfect sense. Yet we've all collectively agreed that those are unwholeso…

> New Geometry Representation might be a fine name for a new format, but you're not going to use its acronym.

I might... the acronym doesn't ring any bells and a Google search doesn't show anything special (if anything, it already shows a bunch of other things - including companies and organizations - using the same letters). What is the issue?

Re: Many packages suddenly disappeared

#158
post #108

Earlier quoted context omitted.

I just tested, and it definitely looks like a troll / hack. > duplexer3@1.0.1 install /Users/foo/Code/foo/node_modules/duplexer3 > echo "To every thing there is a season, and a time to every purpose under the heaven: A time to be born, and a time to die; a time to plant, and a time to pluck up that which is planted; A time to kill, and a time to heal; a time to break down, and a time to build up; A time to weep, and…

They're referencing the Bible: https://www.biblegateway.com/passage/?search=Ecclesiastes+3&...

I’m pretty sure they’re referencing the Byrds song and not the Bible directly:

https://m.youtube.com/watch?feature=youtu.be&v=pKP4cfU28vM

Re: Many packages suddenly disappeared

#159
post #52
post #44

Btw. for those who don't know: Yarn (which is an alternative to npm) uses a global cache [1] on your machine which speeds things up, but probably also protects you from immediate problems in cases like the one currently on progress (because you would probably have a local copy of e.g. require-from-string available). [1] https://yarnpkg.com/lang/en/docs/cli/cache/

Already counting down the days before yarn is considered old and broken and people are recommending switching to the next hot package manager/bundler...

yarn is one of those things coming out of the JS world that is actually really well made. yarn, typescript, react; say what you want about js fatigue, these are rock-solid, well-tested projects that are really good at what they do.

A major reason for the high toolchurn in that ecosystem is how many of those tools are not designed from the ground up, don't quite solve the things they ought to, or solve them in really weird ways (due to the low barrier of entry partly). But that doesn't mean all of it deserves that label.

Post reply on HN