Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Name node installations #271

Open
janpio opened this issue May 12, 2017 · 3 comments
Open

Name node installations #271

janpio opened this issue May 12, 2017 · 3 comments
Projects
Milestone

Comments

@janpio
Copy link

janpio commented May 12, 2017

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.

@coreybutler
Copy link
Owner

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.

image

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.

@janpio
Copy link
Author

janpio commented May 17, 2017

Thanks.

As I read my own suggestion again, here is an idea for a lightweight way to implement something like that:

  • nvm annotate "contains CLI v2.3" (or similar) creates a file nvm.config in the currently used node version's folder.
  • nvm list then reads these and outputs them in the list.

That's it ;)

@coreybutler
Copy link
Owner

Noted and appreciated. I like the annotation concept.

@coreybutler coreybutler modified the milestone: 2.0.0 Jul 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
2.0.0
Backlog
Development

No branches or pull requests

2 participants