11–20 of 65 posts
Earlier quoted context omitted.
I haven't read the article yet, but I would assume they want versioning, history, checksumming and verification. All that stuff is worthwhile, it's just unfortunate npm is such a heavy dependency to achieve it.
Not that heavy if they're already using it though
What, did curl not work?
I haven't read the article yet, but I would assume they want versioning, history, checksumming and verification. All that stuff is worthwhile, it's just unfortunate npm is such a heavy dependency to achieve it.
YUM is almost old enough to drink in Europe.
I need a medium account to read this for some reason.
> "This is your last free member-only story this month. Sign up for Medium and get an extra one" Well, that's about the end of medium I think.
What, did curl not work?
I haven't read the article yet, but I would assume they want versioning, history, checksumming and verification. All that stuff is worthwhile, it's just unfortunate npm is such a heavy dependency to achieve it.
I need a medium account to read this for some reason.
here's the summary: it opens with "We recently migrated our internal CLI tool from Node JS to Golang". It's just a way to keep using the hammer they already had, no matter if the problem is a nail or not. could be titled "how to hack your private npm server to be a OS package manager, because we don't want to learn our OS packaging"
Earlier quoted context omitted.
> "This is your last free member-only story this month. Sign up for Medium and get an extra one" Well, that's about the end of medium I think.
Turn off Javascript. They don't (yet) have an SPA and it degrades appropriately for disabled users.
Why didn't they use the os package manager? Which OS? Their build clearly builds for osx, windows, and Linux.
Earlier quoted context omitted.
here's the summary: it opens with "We recently migrated our internal CLI tool from Node JS to Golang". It's just a way to keep using the hammer they already had, no matter if the problem is a nail or not. could be titled "how to hack your private npm server to be a OS package manager, because we don't want to learn our OS packaging"
Which raises the question: package management is just a bunch of nails; why do I need a specific hammer for each type of nail?
Earlier quoted context omitted.
I haven't read the article yet, but I would assume they want versioning, history, checksumming and verification. All that stuff is worthwhile, it's just unfortunate npm is such a heavy dependency to achieve it.
Debian apt gives all these things and would be less of a heavy dependency.
I bet some day we'll have a Linux distro with npm as the system package manager here on HN.