-
-
Notifications
You must be signed in to change notification settings - Fork 738
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
n fails when there is no internet access and other semi-related issues #404
Comments
|
There were a lot of interesting comments here, thanks @sine9. I came across this issue again, so a status update for future readers.
|
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello n developers! I love
n
and use it to quickly switch versions of node for testing.I was on a plane recently no internet access and n stopped working. After seeing that you needed to specify the exact version number, I attempted to write a shell script wrapper and found other issues worth noting. They are all listed here:
n
to use the latest available for a given semver description if internet access is not available. To test this, try turning off your internet and runningAll of these fail. The only thing that worked was running
n
and pulling the exact version number.n
probably should just fail rather than attempt a command.n ls
gives blank input when there is no internet connection. I can understand why, since "available" is determined by comparing against a list that is unavailable when internet is off, but sincen
can switch between installed versionsn ls
should show only the installed versions when internet access is not available.There is no command to just get a plaintext list of the installed versions.
n
is an interactive tool, redirecting to file or pipe screws with the shell session.n ls
shows in bold but it's difficult to work with that programmatically. Some TTY detection logic may be necessary.the
n
list sorts the0.10
and0.12
series before the0.8
series. That seems to be a bug that will rear its ugly head again if6.10
is reached.How do I remove all older minor or patch versions of node? For example, my computer has a bunch of older node versions and I would like to prune to the latest patch version of the given major version:
The text was updated successfully, but these errors were encountered: