What constitutes an environment?

[marcelklehr]

In an effort to sort out some preliminaries for #3, I suggest to think about what we need to store in the file system, i.e. what is part of an environment.

IMO, we should have separately installable/manageable blobs/containers/envirnments that contain and tie together

• one node version (that's what we're here for)
• ... sepcific to one machine architecture (because of native modules)
• one npm installation (when you want it, you also want it per version; you may do to this installation whatever you want: upgrade it, break it, ignore it, etc.)
• one repository of global modules (native modules again)

Should this buffet of node environements be accessible globally?
Where would the best place be for this buffet to live in the file system?
Would it maybe be more beneficial to store npm separately to allow separate management and thus rapid switching of it?

[ljharb]

npm is a global modules installed in a node version; i think it's probably useful for a version manager to be able to set that up for a given node version, but there's only one global npm for a given node version.

Separately, global modules are by necessity distinct per node version, and must never be shared across them. A choice of node version (including JS engine and architecture) immediately provides a single place where all global modules, including npm, live.