4 Commits

Author SHA1 Message Date
Hsiao-nan Cheung
6031a8ddfb nvs: Delete note due to author's fix. (#2928) 2018-12-27 11:44:31 +01:00
Richard Kuhnt
84a916f87e nvs: Update to version 1.5.2 2018-12-26 21:00:23 +00:00
Hsiao-nan Cheung
4b7f9ce3d4 nvs: Fix output null (#2914)
nvs: Fix output null
2018-12-19 05:55:06 +01:00
Hsiao-nan Cheung
60bfa5fde5 nvs: Add version 1.5.1 (#2886)
Add nvs v1.5.1, a more powerful Node.js versions tool on Windows than nvm-windows made by @jasongin.

- Name: Node Version Switcher
- Description: A cross-platform tool for switching between versions and forks of Node.js
- Version: 1.5.1
- Homepage: https://github.com/jasongin/nvs
- Basic usage
  - To add the latest version of node:
    ```powershell
    $ nvs add latest
    ```
  - Or to add the latest LTS version of node:
    ```powershell
    $ nvs add lts
    ```
  - Then run the `nvs use` command to add a version of node to your PATH for the current shell:
    ```powershell
    $ nvs use lts
    PATH += ~/.nvs/node/10.14.2/x64
    ```
  - To add it to PATH permanently, use `nvs link`:
    ```powershell
    $ nvs link lts
    ```
- Known Issue: Sometimes nvs will show an `EPERM: operation not permitted.` error during first adding some Node.js version, and it is due to JavaScript `fs.renameSync` function. The author hasn't been able to reproduce it himself (https://github.com/jasongin/nvs/issues/79#issuecomment-352277210), and in my practice, `nvs rm` and `nvs add` again should solve the problem. This only occurs in first `nvs add` run after re/install nvs.
2018-12-13 13:12:48 +01:00