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

[Doc] Address symbolic link issue in nvm_die_on_prefix error message #1387

Closed
wants to merge 1 commit into from
Closed

Conversation

MrOrz
Copy link

@MrOrz MrOrz commented Jan 18, 2017

Fixes #1385 .

Not sure if the wording is clear enough. Feel free to rephrase them!

@ljharb ljharb changed the title [Doc] Address symbolic link issue in the error message of… [Doc] Address symbolic link issue in nvm_die_on_prefix error message Jan 18, 2017
@@ -2010,6 +2010,7 @@ nvm_die_on_prefix() {
else
nvm_err "Run \`$NVM_COMMAND\` to unset it."
fi
nvm_err "If \"$NVM_NPM_PREFIX\" is actually inside \"$NVM_DIR\" directory, please modify your NVM_DIR to make sure there is no any symbolic links."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is fine, I think - although I wonder if there's any POSIX-compatible way this can be detected?

@ljharb
Copy link
Member

ljharb commented Sep 29, 2021

@MrOrz unfortunately it seems you've deleted your fork, so i can't rebase and land this. Any chance you could try to restore it, and recreate the branch?

@ljharb ljharb marked this pull request as draft September 29, 2021 16:13
@MrOrz
Copy link
Author

MrOrz commented Oct 4, 2021

Hello @ljharb thanks for taking a look. I did a rebase and see that in master branch, NVM_NPM_PREFIX is no longer used. Therefore I think the changes made in 2017 is not relevant now.

Personally I did not encounter such issue for quite a few years, so I am not sure if I can reproduce the issue now.

@ljharb
Copy link
Member

ljharb commented Oct 4, 2021

Now it's called NVM_CONFIG_VALUE, but if you aren't encountering the issue any more, I guess we'll close this. Please file an issue if it occurs again.

@ljharb ljharb closed this Oct 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Adding descriptions about symlinks in the 'nvm is not compatible with the npm config "prefix" option' error
3 participants