3 ms·

Yeah, this just seems like a pain in the ass that could've been easily avoided.

• iainmerrick 1y ago
  From my perspective, I'm totally happy to use pnpm to install and manage this. Even if it were a native tool, NPM might be a decent distribution mechanism (see e.g. esbuild). Obviously everybody's requirements differ, but Node seems like a pretty reasonable platform for this.
  • danielbln 1y ago
    Also throwing Volta (written in Rust, because of course it is) into the ring. It's the uv of the Node world.
• jstummbillig 1y ago
  It feels like you are creating a considerable fraction of the pain by taking offense with simply using npm.
  • evilduck 1y ago
    As a longtime user of NPM but overall fan of JS and TS and even its runtimes, NPM is a dumpster fire and forcing end users to use it is brittle, lazy, and hostile. A small set of dependencies will easily result in thousands (if not tens of thousands) of transitive dependency files being installed. If you have to run end point protection that will blast your CPU with load and it makes moving or even deleting that folder needlessly slow. It also makes the hosting burden of NPM (nusers) who must all install dependencies instead of (nCI instances), which isn't very nice to our hosts. Dealing with that once during your build phase and then packaging that mess up is the nicer way to go about distributing things depending on NPM to end users.
    • frollogaston 1y ago
      I ran the npm install command in their readme, it took a few seconds, then it worked. Subsequent runs don't have to redownload stuff. It's 127MB, which is big for an executable but not a real problem. Where is the painful part?