Can this be used to create/download npm as a standalone executable?

[guest271314]

Operating system and version:

Linux

In the archive download we have various files named "npm", some in "/node/lib/node_modules/npm/bin/".

Simple question:

Can this (nvm) be used to create/download npm as a standalone executable if such an executable exists?

[ljharb]

No, of course not. npm can’t ever work that way, and nvm is a node version manager.

[guest271314]

So there is no standalone npm executable or shell script that either Node.js nor GitHub publishes, correct?

[guest271314]

npm can’t ever work that way

So, if I'm reading your restriction on the functionality of npm correct, we can't ever create a single executable application --experimental-sea-config=... with node and npm compiled into a single executable?

So we don't have to carry around all the bagge of the default Node.js release archives, and be consistent with how Deno, Bun, QuickJS https://bellard.org/quickjs/binary_releases/ provide a way to get directly to the JavaScript runtime executable without a bunch of other folders and files.

[ljharb]

I’m sure you can, but then it wouldn’t be npm anymore.

You’ve exhausted his discussion already in node and npm’s repos; there’s nowhere left to have it, and here certainly isn’t the place.

[guest271314]

I’m sure you can, but then it wouldn’t be npm anymore.

I don't understand that.

You’ve exhausted his discussion already in node and npm’s repos; there’s nowhere left to have it, and here certainly isn’t the place.

Wow. Here I am just asking questions, in a civil manner.

Why do even reply to me when you have contempt for my use cases? You know you can recuse yourself and ask one of your colleagues to reply.

Anyway, thanks for your answer. Have a great day.

[ljharb]

I have no colleagues; I’m the only nvm maintainer.

[guest271314]

Oh, well then. I suppose I have to just keep asking questions and getting your answers for Node.js world.

I thought I was asking about nvm, not "You’ve exhausted his discussion already in node and npm’s repos; there’s nowhere left to have it, and here certainly isn’t the place.".

I decide when I have exhausted my remedies.

I'm trying to eliminate npm from the equation. There's the Node.js way of doing things then there's the rest of JavaScript runtime world.

Take a GitHub repository that uses CommonJS exclusively. Why install npm (npm-cli), whatever, when all of the dependencies are available on jsDelivr as Ecmascript Modules that can be dynamically imported in memory rather than hardcoding in the repository?

[ljharb]

npm can’t be eliminated from the equation when you’re dealing with JavaScript ¯\_(ツ)_/¯

I’m going to go ahead and lock this, because past experience shows this will continue being off topic. I answered your question about nvm.