nsnvm

commit a0edcab849ae52b77217516d370b6966e3964dbc
parent 904cd2d46e77d34fca62eeddd8212e49b23a72dc
Author: Nuño Sempere <nuno.sempere@protonmail.com>
Date:   Tue, 18 Apr 2023 10:51:56 -0400

fix: warn about globally installed packages.
Diffstat:
M
README.md
 | 
6
+++++-

1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/README.md b/README.md
@@ -1,4 +1,4 @@
-NUÑO's STUPID NODE VERSION MANAGER
+Nuño's Stupid Node Version Manager
 ==================================
 
 ## The problem
@@ -31,6 +31,10 @@ Read the `nsnvm.sh` file, then execute it like:
 
 Make sure that you pass it one argument and that it is a correct node version number: there is no error checking. You can check node versions [here](https://nodejs.org/dist/index.json) or [here](https://nodejs.org/en/download/releases/)
 
+## Downsides
+
+This setup will wreck your existing global node package installations, i.e., packages installed with `npm -g package_name`. To fix this, install a package again and look into `$HOME/.nsnvm/.../npm` for the location of the package, and wrap it in a bash alias. 
+
 ## Contributions
 
 Contributions are welcome as long as they keep with the overall theme of simplicity. In particular, some small amount of error checking—e.g., checking that the version exists or that arguments aren't empy—would be fine.