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

[spam] #2735

Closed
wants to merge 1,462 commits into from
Closed

[spam] #2735

wants to merge 1,462 commits into from

Conversation

ImaginalaticWizardry
Copy link

I am trying to figure this out.

alnorris and others added 30 commits December 6, 2016 15:14
Allow newbies to get a quick understanding of how `nvm` works right from the start.
This uses the npm package `markdown-link-check` to check if all the links in the documentation are alive.
Since markdown-link-check hasn't support relative links, to make the
test passed, move this link to use absolute URL so that we can introduce
the new test. cc tcort/markdown-link-check#10
 - fix test 'Running "nvm ls" should display all installed versions.': only expect versions created by this test, but no versions created by other tests
 - Only works for common aliases like `default`, `system`, `node`, `lts/*`, `iojs` etc.
 - Prevent unnecessary running of `nvm use`
Adds the following information to the "Migrating global packages while installing" section:
- notification that the npm package is explicitly not updated when using the --reinstall-packages-from flag
- information about the --latest-npm flag
- recovery instructions if a user has already updated node with an incompatible npm version
With the environment variable XDG_CONFIG_HOME set, the installation
script uses the directory $XDG_CONFIG_HOME/nvm now. Before the change
the variable's value with "/nvm" cut off was used, which usually results
in an installation without any subdirectory.
ljharb and others added 23 commits November 25, 2021 19:35
If the node version is below 16.0.0 then nvm will select x86_64 architecture, else arm64 architecture.
`nvm install` fails with "Binary download failed, trying source" when
- running on Bash;
- errtrace (`set -E`) is enabled;
- an ERR trap uses `exit` to return a non-zero status; and
- /sbin/init doesn't exist.

Resolved by moving `ls -dl /sbin/init` to the following `if` statement.
In this context, returning non-zero isn't an error and the ERR trap
isn't executed.
@ImaginalaticWizardry
Copy link
Author

👍😍

@ljharb
Copy link
Member

ljharb commented Feb 2, 2022

@ImaginalaticWizardry please don't open PRs at all until you understand how github works, but also this and #2736 are both spam.

@ljharb ljharb closed this Feb 2, 2022
@ljharb ljharb added the non-issue / invalid This isn't relevant to nvm, or turned out to be something unrelated. label Feb 2, 2022
@ljharb ljharb changed the title figures [spam] Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
non-issue / invalid This isn't relevant to nvm, or turned out to be something unrelated.
Projects
None yet
Development

Successfully merging this pull request may close these issues.