You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now the node installations are identified by their version number. This totally makes sense if the version is all you care about. But if you really want to know what is installed inside that node (via npm install -g) you have no way of knowing.
It would be great if we maybe could "name" our node installations that are shown together with the version numbers on nvm list.
The text was updated successfully, but these errors were encountered:
First, I think this is a great idea. However; I think this is more of a workflow thing and I see NVM4W being more utilitarian. Implementing something like this requires metadata about each installation, which isn't a bad thing, but I think this is a "tip of the iceburg" situation with much more to it.
That said, I have been prototyping a visual desktop app for managing Node environments in my spare time. Since my time is pretty limited right now, not a lot of progress has been made. However; I do have it detecting npm modules and different versions of Node.
I'm also experimenting with a JSON reporting feature in NVM4W. I'm not yet sure if it really makes to have this in NVM4W or the desktop tool, but the broader point is I'm experimenting with a few different ideas around this subject.
Right now the node installations are identified by their version number. This totally makes sense if the version is all you care about. But if you really want to know what is installed inside that node (via
npm install -g
) you have no way of knowing.It would be great if we maybe could "name" our node installations that are shown together with the version numbers on
nvm list
.The text was updated successfully, but these errors were encountered: