Skip to content

Instantly share code, notes, and snippets.

@ktdung

ktdung/installing-node-with-nvm.md

Forked from d2s/installing-node-with-nvm.md
Created August 22, 2019 06:21
Show Gist options
  • Save ktdung/4245f52fbb85b4f1fdac1aff5ca5ee01 to your computer and use it in GitHub Desktop.
Save ktdung/4245f52fbb85b4f1fdac1aff5ca5ee01 to your computer and use it in GitHub Desktop.
Download ZIP

Revisions

  1. @d2s d2s revised this gist Aug 21, 2019. 1 changed file with 4 additions and 4 deletions.
    8 changes: 4 additions & 4 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -38,10 +38,10 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.16.3`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.8.1`
    - `nvm install v12.9.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.16.3` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.3)
    - `nvm alias default v12.8.1` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.8.1)
    - `nvm alias default v12.9.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.9.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.16.2` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

    @@ -55,15 +55,15 @@ If you already have previous version of Node.js installed with nvm, you can migr
    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v10.16.2`
    - `nvm reinstall-packages v12.8.0`
    - `nvm reinstall-packages v12.8.1`

    ### Deleting old Node.js versions

    - Look what versions are installed:
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.16.2`
    - `nvm uninstall v12.8.0`
    - `nvm uninstall v12.8.1`

    ### Updating outdated packages

  2. @d2s d2s revised this gist Aug 16, 2019. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -38,7 +38,7 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.16.3`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.8.0`
    - `nvm install v12.8.1`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.16.3` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.3)
    - `nvm alias default v12.8.1` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.8.1)
  3. @d2s d2s revised this gist Aug 16, 2019. 1 changed file with 4 additions and 4 deletions.
    8 changes: 4 additions & 4 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -36,11 +36,11 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    5. List what versions of Node are currently installed (probably none).
    - `nvm ls`
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.16.2`
    - `nvm install v10.16.3`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.8.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.16.2` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.2)
    - `nvm alias default v10.16.3` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.3)
    - `nvm alias default v12.8.1` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.8.1)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.16.2` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.
    @@ -54,15 +54,15 @@ If you already have previous version of Node.js installed with nvm, you can migr

    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v10.16.1`
    - `nvm reinstall-packages v10.16.2`
    - `nvm reinstall-packages v12.8.0`

    ### Deleting old Node.js versions

    - Look what versions are installed:
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.16.1`
    - `nvm uninstall v10.16.2`
    - `nvm uninstall v12.8.0`

    ### Updating outdated packages
  4. @d2s d2s revised this gist Aug 15, 2019. 1 changed file with 4 additions and 4 deletions.
    8 changes: 4 additions & 4 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -41,9 +41,9 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    - `nvm install v12.8.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.16.2` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.2)
    - `nvm alias default v12.8.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.8.0)
    - `nvm alias default v12.8.1` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.8.1)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.16.1` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.
    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.16.2` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

    You can find a lot of packages from the [npm](https://www.npmjs.com/) package repository. Have a good time with the freshly installed tools.

    @@ -55,15 +55,15 @@ If you already have previous version of Node.js installed with nvm, you can migr
    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v10.16.1`
    - `nvm reinstall-packages v12.7.0`
    - `nvm reinstall-packages v12.8.0`

    ### Deleting old Node.js versions

    - Look what versions are installed:
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.16.1`
    - `nvm uninstall v12.7.0`
    - `nvm uninstall v12.8.0`

    ### Updating outdated packages

  5. @d2s d2s revised this gist Aug 7, 2019. 1 changed file with 8 additions and 8 deletions.
    16 changes: 8 additions & 8 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -36,12 +36,12 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    5. List what versions of Node are currently installed (probably none).
    - `nvm ls`
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.16.1`
    - `nvm install v10.16.2`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.7.0`
    - `nvm install v12.8.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.16.1` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.1)
    - `nvm alias default v12.7.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.7.0)
    - `nvm alias default v10.16.2` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.2)
    - `nvm alias default v12.8.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.8.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.16.1` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

    @@ -54,16 +54,16 @@ If you already have previous version of Node.js installed with nvm, you can migr

    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v10.16.0`
    - `nvm reinstall-packages v12.6.0`
    - `nvm reinstall-packages v10.16.1`
    - `nvm reinstall-packages v12.7.0`

    ### Deleting old Node.js versions

    - Look what versions are installed:
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.16.0`
    - `nvm uninstall v12.6.0`
    - `nvm uninstall v10.16.1`
    - `nvm uninstall v12.7.0`

    ### Updating outdated packages

  6. @d2s d2s revised this gist Aug 4, 2019. 1 changed file with 2 additions and 0 deletions.
    2 changes: 2 additions & 0 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -8,6 +8,8 @@ Previous versions of these install instructions had been tested with:
    - [Ubuntu 17.04 (Zesty Zapus)](http://releases.ubuntu.com/xenial/)
    - [Ubuntu 16.04 LTS (Xenial Xerus)](http://releases.ubuntu.com/xenial/)
    - [Ubuntu 14.04.3 LTS (Trusty)](http://releases.ubuntu.com/trusty/)
    - [macOS 10.14.6 (Mojave)](https://apple.wikia.com/wiki/MacOS_10.14.6)
    - [macOS 10.13.6 (High Sierra)](https://apple.wikia.com/wiki/MacOS_10.13.6)
    - [macOS 10.12.6 (Sierra)](https://apple.wikia.com/wiki/MacOS_10.12.6)
    - [OS X 10.11.6 (El Capitan)](https://apple.wikia.com/wiki/OS_X_10.11.6)

  7. @d2s d2s revised this gist Aug 4, 2019. 1 changed file with 16 additions and 16 deletions.
    32 changes: 16 additions & 16 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -34,27 +34,35 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    5. List what versions of Node are currently installed (probably none).
    - `nvm ls`
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.16.0`
    - `nvm install v10.16.1`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.7.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.16.0` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.0)
    - `nvm alias default v10.16.1` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.1)
    - `nvm alias default v12.7.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.7.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.16.0` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.
    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.16.1` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

    You can find a lot of packages from the [npm](https://www.npmjs.com/) website. Have a good time with the tools.
    You can find a lot of packages from the [npm](https://www.npmjs.com/) package repository. Have a good time with the freshly installed tools.


    ## Upgrading from previous version of Node.js
    ## Migrating packages from the previously installed Node.js versions

    If you already have previous version of Node.js installed with nvm, you can upgrade to a different version with these steps.
    If you already have previous version of Node.js installed with nvm, you can migrate packages from previously installed Node.js versions.

    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v10.15.3`
    - `nvm reinstall-packages v10.16.0`
    - `nvm reinstall-packages v12.6.0`

    ### Deleting old Node.js versions

    - Look what versions are installed:
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.16.0`
    - `nvm uninstall v12.6.0`

    ### Updating outdated packages

    #### List what (top level) packages are installed globally
    @@ -82,12 +90,4 @@ After installation of Node v10.x (or similar), it can be a good idea to recompil
    ```sh
    cd PROJECT_NAME
    npm rebuild
    ```

    ## Deleting old Node.js versions

    - Look what versions are installed:
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.15.3`
    - `nvm uninstall v12.6.0`
    ```
  8. @d2s d2s revised this gist Jul 23, 2019. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -90,4 +90,4 @@ npm rebuild
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.15.3`
    - `nvm uninstall v12.5.0`
    - `nvm uninstall v12.6.0`
  9. @d2s d2s revised this gist Jul 23, 2019. 1 changed file with 3 additions and 3 deletions.
    6 changes: 3 additions & 3 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -36,10 +36,10 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.16.0`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.6.0`
    - `nvm install v12.7.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.16.0` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.0)
    - `nvm alias default v12.6.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.6.0)
    - `nvm alias default v12.7.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.7.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.16.0` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

    @@ -53,7 +53,7 @@ If you already have previous version of Node.js installed with nvm, you can upgr
    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v10.15.3`
    - `nvm reinstall-packages v12.5.0`
    - `nvm reinstall-packages v12.6.0`

    ### Updating outdated packages

  10. @d2s d2s revised this gist Jul 3, 2019. 1 changed file with 4 additions and 4 deletions.
    8 changes: 4 additions & 4 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -36,10 +36,10 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.16.0`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.5.0`
    - `nvm install v12.6.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.16.0` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.0)
    - `nvm alias default v12.5.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.5.0)
    - `nvm alias default v12.6.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.6.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.16.0` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

    @@ -53,7 +53,7 @@ If you already have previous version of Node.js installed with nvm, you can upgr
    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v10.15.3`
    - `nvm reinstall-packages v12.4.0`
    - `nvm reinstall-packages v12.5.0`

    ### Updating outdated packages

    @@ -90,4 +90,4 @@ npm rebuild
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.15.3`
    - `nvm uninstall v12.4.0`
    - `nvm uninstall v12.5.0`
  11. @d2s d2s revised this gist Jul 2, 2019. 1 changed file with 4 additions and 4 deletions.
    8 changes: 4 additions & 4 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -4,10 +4,10 @@ A quick guide on how to setup Node.js development environment.

    Previous versions of these install instructions had been tested with:
    - [Ubuntu on WSL (Windows Subsystem for Linux)](https://docs.microsoft.com/en-us/windows/wsl/about)
    - [Ubuntu 18.04 LTS (Bionic Beaver)](https://releases.ubuntu.com/bionic/)
    - [Ubuntu 17.04 (Zesty Zapus)](https://releases.ubuntu.com/xenial/)
    - [Ubuntu 16.04 LTS (Xenial Xerus)](https://releases.ubuntu.com/xenial/)
    - [Ubuntu 14.04.3 LTS (Trusty)](https://releases.ubuntu.com/trusty/)
    - [Ubuntu 18.04 LTS (Bionic Beaver)](http://releases.ubuntu.com/bionic/)
    - [Ubuntu 17.04 (Zesty Zapus)](http://releases.ubuntu.com/xenial/)
    - [Ubuntu 16.04 LTS (Xenial Xerus)](http://releases.ubuntu.com/xenial/)
    - [Ubuntu 14.04.3 LTS (Trusty)](http://releases.ubuntu.com/trusty/)
    - [macOS 10.12.6 (Sierra)](https://apple.wikia.com/wiki/MacOS_10.12.6)
    - [OS X 10.11.6 (El Capitan)](https://apple.wikia.com/wiki/OS_X_10.11.6)

  12. @d2s d2s revised this gist Jul 2, 2019. 1 changed file with 6 additions and 6 deletions.
    12 changes: 6 additions & 6 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -4,12 +4,12 @@ A quick guide on how to setup Node.js development environment.

    Previous versions of these install instructions had been tested with:
    - [Ubuntu on WSL (Windows Subsystem for Linux)](https://docs.microsoft.com/en-us/windows/wsl/about)
    - [Ubuntu 18.04 LTS (Bionic Beaver)](http://releases.ubuntu.com/bionic/)
    - [Ubuntu 17.04 (Zesty Zapus)](http://releases.ubuntu.com/xenial/)
    - [Ubuntu 16.04 LTS (Xenial Xerus)](http://releases.ubuntu.com/xenial/)
    - [Ubuntu 14.04.3 LTS (Trusty)](http://releases.ubuntu.com/trusty/)
    - [macOS 10.12.6 (Sierra)](http://apple.wikia.com/wiki/MacOS_10.12.6)
    - [OS X 10.11.6 (El Capitan)](http://apple.wikia.com/wiki/OS_X_10.11.6)
    - [Ubuntu 18.04 LTS (Bionic Beaver)](https://releases.ubuntu.com/bionic/)
    - [Ubuntu 17.04 (Zesty Zapus)](https://releases.ubuntu.com/xenial/)
    - [Ubuntu 16.04 LTS (Xenial Xerus)](https://releases.ubuntu.com/xenial/)
    - [Ubuntu 14.04.3 LTS (Trusty)](https://releases.ubuntu.com/trusty/)
    - [macOS 10.12.6 (Sierra)](https://apple.wikia.com/wiki/MacOS_10.12.6)
    - [OS X 10.11.6 (El Capitan)](https://apple.wikia.com/wiki/OS_X_10.11.6)

    ## Install nvm for managing Node.js versions

  13. @d2s d2s revised this gist Jun 27, 2019. 1 changed file with 8 additions and 10 deletions.
    18 changes: 8 additions & 10 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -55,16 +55,6 @@ If you already have previous version of Node.js installed with nvm, you can upgr
    - `nvm reinstall-packages v10.15.3`
    - `nvm reinstall-packages v12.4.0`


    ## Deleting old Node.js versions

    - Look what versions are installed:
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.15.3`
    - `nvm uninstall v12.4.0`


    ### Updating outdated packages

    #### List what (top level) packages are installed globally
    @@ -93,3 +83,11 @@ After installation of Node v10.x (or similar), it can be a good idea to recompil
    cd PROJECT_NAME
    npm rebuild
    ```

    ## Deleting old Node.js versions

    - Look what versions are installed:
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.15.3`
    - `nvm uninstall v12.4.0`
  14. @d2s d2s revised this gist Jun 27, 2019. 1 changed file with 11 additions and 12 deletions.
    23 changes: 11 additions & 12 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -36,10 +36,10 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.16.0`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.4.0`
    - `nvm install v12.5.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.16.0` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.0)
    - `nvm alias default v12.4.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.4.0)
    - `nvm alias default v12.5.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.5.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.16.0` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

    @@ -53,9 +53,17 @@ If you already have previous version of Node.js installed with nvm, you can upgr
    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v10.15.3`
    - `nvm reinstall-packages v12.3.1`
    - `nvm reinstall-packages v12.4.0`


    ## Deleting old Node.js versions

    - Look what versions are installed:
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.15.3`
    - `nvm uninstall v12.4.0`


    ### Updating outdated packages

    @@ -85,12 +93,3 @@ After installation of Node v10.x (or similar), it can be a good idea to recompil
    cd PROJECT_NAME
    npm rebuild
    ```


    ## Deleting old Node.js versions

    - Look what versions are installed:
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.15.3`
    - `nvm uninstall v12.3.1`
  15. @d2s d2s revised this gist Jun 4, 2019. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -36,10 +36,10 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.16.0`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install 12.4.0`
    - `nvm install v12.4.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.16.0` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.0)
    - `nvm alias default 12.4.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.4.0)
    - `nvm alias default v12.4.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.4.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.16.0` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

  16. @d2s d2s revised this gist Jun 4, 2019. 1 changed file with 5 additions and 5 deletions.
    10 changes: 5 additions & 5 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -36,12 +36,12 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.16.0`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.3.1`
    - `nvm install 12.4.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.16.0` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.0)
    - `nvm alias default v12.3.1` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.3.0)
    - `nvm alias default 12.4.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.4.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.15.3` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.
    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.16.0` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

    You can find a lot of packages from the [npm](https://www.npmjs.com/) website. Have a good time with the tools.

    @@ -53,7 +53,7 @@ If you already have previous version of Node.js installed with nvm, you can upgr
    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v10.15.3`
    - `nvm reinstall-packages v12.3.0`
    - `nvm reinstall-packages v12.3.1`



    @@ -93,4 +93,4 @@ npm rebuild
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.15.3`
    - `nvm uninstall v12.3.0`
    - `nvm uninstall v12.3.1`
  17. @d2s d2s revised this gist May 29, 2019. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -92,5 +92,5 @@ npm rebuild
    - Look what versions are installed:
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.15.2`
    - `nvm uninstall v10.15.3`
    - `nvm uninstall v12.3.0`
  18. @d2s d2s revised this gist May 29, 2019. 1 changed file with 3 additions and 2 deletions.
    5 changes: 3 additions & 2 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -34,11 +34,11 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    5. List what versions of Node are currently installed (probably none).
    - `nvm ls`
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.15.3`
    - `nvm install v10.16.0`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.3.1`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.15.3` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.15.3)
    - `nvm alias default v10.16.0` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.16.0)
    - `nvm alias default v12.3.1` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.3.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.15.3` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.
    @@ -52,6 +52,7 @@ If you already have previous version of Node.js installed with nvm, you can upgr

    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v10.15.3`
    - `nvm reinstall-packages v12.3.0`


  19. @d2s d2s revised this gist May 22, 2019. 1 changed file with 5 additions and 5 deletions.
    10 changes: 5 additions & 5 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -36,10 +36,10 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.15.3`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.3.0`
    - `nvm install v12.3.1`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.15.3` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.15.3)
    - `nvm alias default v12.3.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.3.0)
    - `nvm alias default v12.3.1` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.3.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.15.3` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

    @@ -52,7 +52,7 @@ If you already have previous version of Node.js installed with nvm, you can upgr

    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v12.2.0`
    - `nvm reinstall-packages v12.3.0`



    @@ -91,5 +91,5 @@ npm rebuild
    - Look what versions are installed:
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.14.1`
    - `nvm uninstall v12.2.0`
    - `nvm uninstall v10.15.2`
    - `nvm uninstall v12.3.0`
  20. @d2s d2s revised this gist May 21, 2019. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -1,4 +1,4 @@
    # Installing Node.js with nvm to Linux & macOS
    # Installing Node.js with nvm to Linux & macOS & WSL

    A quick guide on how to setup Node.js development environment.

  21. @d2s d2s revised this gist May 21, 2019. 1 changed file with 4 additions and 4 deletions.
    8 changes: 4 additions & 4 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -36,10 +36,10 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.15.3`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.2.0`
    - `nvm install v12.3.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.15.3` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.15.3)
    - `nvm alias default v12.2.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.2.0)
    - `nvm alias default v12.3.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.3.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.15.3` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

    @@ -52,7 +52,7 @@ If you already have previous version of Node.js installed with nvm, you can upgr

    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v12.1.0`
    - `nvm reinstall-packages v12.2.0`



    @@ -92,4 +92,4 @@ npm rebuild
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.14.1`
    - `nvm uninstall v12.1.0`
    - `nvm uninstall v12.2.0`
  22. @d2s d2s revised this gist May 7, 2019. 1 changed file with 1 addition and 0 deletions.
    1 change: 1 addition & 0 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -92,3 +92,4 @@ npm rebuild
    - `nvm ls`
    - Delete an older version (if it is no longer used in some of your projects):
    - `nvm uninstall v10.14.1`
    - `nvm uninstall v12.1.0`
  23. @d2s d2s revised this gist May 7, 2019. 1 changed file with 3 additions and 3 deletions.
    6 changes: 3 additions & 3 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -36,10 +36,10 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.15.3`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.1.0`
    - `nvm install v12.2.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.15.3` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.15.3)
    - `nvm alias default v12.1.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.1.0)
    - `nvm alias default v12.2.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.2.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.15.3` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

    @@ -52,7 +52,7 @@ If you already have previous version of Node.js installed with nvm, you can upgr

    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version:
    - `nvm reinstall-packages v12.0.0`
    - `nvm reinstall-packages v12.1.0`



  24. @d2s d2s revised this gist Apr 30, 2019. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -22,7 +22,7 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    - `wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash`
    - The script clones the nvm repository to `~/.nvm` and adds the source line to your profile (`~/.bash_profile`, `~/.zshrc,` `~/.profile,` or `~/.bashrc`). (You might want/need to add the source loading line by yourself, if the automated install tool does not add it for you.)
    ```sh
    export NVM_DIR="${XDG_CONFIG_HOME/:-$HOME/.}nvm"
    export NVM_DIR="$HOME/.nvm"
    [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm
    [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion
    ```
  25. @d2s d2s revised this gist Apr 30, 2019. 1 changed file with 0 additions and 1 deletion.
    1 change: 0 additions & 1 deletion installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -22,7 +22,6 @@ The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other insta
    - `wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash`
    - The script clones the nvm repository to `~/.nvm` and adds the source line to your profile (`~/.bash_profile`, `~/.zshrc,` `~/.profile,` or `~/.bashrc`). (You might want/need to add the source loading line by yourself, if the automated install tool does not add it for you.)
    ```sh
    export NVM_DIR="$HOME/.nvm"
    export NVM_DIR="${XDG_CONFIG_HOME/:-$HOME/.}nvm"
    [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm
    [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion
  26. @d2s d2s revised this gist Apr 30, 2019. 1 changed file with 2 additions and 2 deletions.
    4 changes: 2 additions & 2 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -13,10 +13,10 @@ Previous versions of these install instructions had been tested with:

    ## Install nvm for managing Node.js versions

    The reason for using [nvm](https://github.com/creationix/nvm) instead of other install types is mainly in how easy it is to have multiple versions of Node.js (if needed) without too much of extra complexity. Sometimes applications might require a certain version of Node.js to work, so having the flexibility of using specific versions can save a lot of time from you.
    The reason for using [nvm](https://github.com/nvm-sh/nvm) instead of other install types is mainly in how easy it is to have multiple versions of Node.js (if needed) without too much of extra complexity. Sometimes applications might require a certain version of Node.js to work, so having the flexibility of using specific versions can save a lot of time from you.

    1. Open new Terminal window.
    2. Run [nvm](https://github.com/creationix/nvm) installer
    2. Run [nvm](https://github.com/nvm-sh/nvm) installer
    - ...with _either_ curl *or* wget.
    - `curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash`
    - `wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash`
  27. @d2s d2s revised this gist Apr 30, 2019. 1 changed file with 3 additions and 2 deletions.
    5 changes: 3 additions & 2 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -18,11 +18,12 @@ The reason for using [nvm](https://github.com/creationix/nvm) instead of other i
    1. Open new Terminal window.
    2. Run [nvm](https://github.com/creationix/nvm) installer
    - ...with _either_ curl *or* wget.
    - `curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.11/install.sh | bash`
    - `wget -qO- https://raw.githubusercontent.com/creationix/nvm/v0.33.11/install.sh | bash`
    - `curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash`
    - `wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.34.0/install.sh | bash`
    - The script clones the nvm repository to `~/.nvm` and adds the source line to your profile (`~/.bash_profile`, `~/.zshrc,` `~/.profile,` or `~/.bashrc`). (You might want/need to add the source loading line by yourself, if the automated install tool does not add it for you.)
    ```sh
    export NVM_DIR="$HOME/.nvm"
    export NVM_DIR="${XDG_CONFIG_HOME/:-$HOME/.}nvm"
    [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm
    [ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion" # This loads nvm bash_completion
    ```
  28. @d2s d2s revised this gist Apr 29, 2019. 1 changed file with 5 additions and 5 deletions.
    10 changes: 5 additions & 5 deletions installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -35,11 +35,11 @@ The reason for using [nvm](https://github.com/creationix/nvm) instead of other i
    - `nvm ls`
    6. Install latest [Node.js](https://nodejs.org/en/) LTS release (recommended for production usage).
    - `nvm install v10.15.3`
    7. Install Current [Node.js](https://nodejs.org/en/) release with latest features (for testing the future features of Node).
    - `nvm install v12.0.0`
    7. Install Current [Node.js](https://nodejs.org/en/) Current release with latest features (for testing new feature improvements).
    - `nvm install v12.1.0`
    8. If you want to change the default Node version later, you can run a command to adjust it.
    - `nvm alias default v10.15.3` (when you work with production quality projects) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V10.md#10.15.3)
    - `nvm alias default v12.0.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.0.0)
    - `nvm alias default v12.1.0` (when you want to test the latest features of Node.js) [changelog](https://github.com/nodejs/node/blob/master/doc/changelogs/CHANGELOG_V12.md#12.1.0)

    It is also possible to select what Node.js version is used per project basis, by running `nvm use v10.15.3` (or another version number) on the directory where the individual project is located. One way to do that is to create small Bash shell script for enabling the right environment when needed, so you would not have to remember what exact version was needed.

    @@ -51,8 +51,8 @@ You can find a lot of packages from the [npm](https://www.npmjs.com/) website. H
    If you already have previous version of Node.js installed with nvm, you can upgrade to a different version with these steps.

    - Open new Terminal window (to make sure you have latest Node.js version active in your command line environment).
    - Linking global packages from previous version (at this example, `v10._._`).
    - `nvm reinstall-packages v10.15.1`
    - Linking global packages from previous version:
    - `nvm reinstall-packages v12.0.0`



  29. @d2s d2s revised this gist Apr 23, 2019. 1 changed file with 1 addition and 1 deletion.
    2 changes: 1 addition & 1 deletion installing-node-with-nvm.md
    View file
    Original file line number Diff line number Diff line change
    @@ -3,7 +3,7 @@
    A quick guide on how to setup Node.js development environment.

    Previous versions of these install instructions had been tested with:
    - [WSL (Windows Subsystem for Linux)](https://docs.microsoft.com/en-us/windows/wsl/about)
    - [Ubuntu on WSL (Windows Subsystem for Linux)](https://docs.microsoft.com/en-us/windows/wsl/about)
    - [Ubuntu 18.04 LTS (Bionic Beaver)](http://releases.ubuntu.com/bionic/)
    - [Ubuntu 17.04 (Zesty Zapus)](http://releases.ubuntu.com/xenial/)
    - [Ubuntu 16.04 LTS (Xenial Xerus)](http://releases.ubuntu.com/xenial/)
  30. @d2s d2s revised this gist Apr 23, 2019. No changes.