-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
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
Feature Request: install a custom local build of nodejs #2218
Comments
@ljharb 👋 |
this seems to work, would be nice to support a prefix like iojs (maybe # from node dir
tools/install.py install /home/xyz/.nvm/versions/node/ v100.0.4
nvm use v100.0.4 |
So, any workarounds are something that are highly likely to break with future nvm/node versions; I'd suggest avoiding those. All In general, the number of people on the planet who will be compiling their own version of node and also needing to test it separately from a system version of node is likely just barely beyond the single digits, so I'm hesitant to add complexity to nvm unless it's going to benefit a significant percentage of users. |
(similar to #1053) |
This comment has been minimized.
This comment has been minimized.
Dirty solution: # Install custom node as 1.9.0 version. Or choose any version number as you like.
mkdir ~/.nvm/node/v1.9.0
# Make symbolic link to bin dir
ln -s /your/path/to/node/bin ~/.nvm/node/v1.9.0/bin
# Make alias to simply switching
nvm alias g v1.9.0
# Use custom local version
nvm use g |
I would kind of like to reference the node and npm installed by my gradle plugin. Doing something like Would be even better if I didn't have to update it every time I updated the node/npm versions set in my gradle file ( |
First: I love
nvm
, its amazing, I use it all the time. 😸I'm experimenting with building forks of nodejs.
I'd like to be able to add these builds to nvm's locally installed versions.
here's what I imagine the usage looks like
I'd expect it to copy the built release so that it doesn't change when I rebuild.
I don't have strong opinions about how the version number works.
Is this currently possible? if not, does this seem reasonable?
The text was updated successfully, but these errors were encountered: