From 890fbb5581b90be206da275b78d06da1231a717a Mon Sep 17 00:00:00 2001 From: jjangga0214 Date: Fri, 15 Feb 2019 11:11:01 +0900 Subject: [PATCH] Update README: sync node release schedule url --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 48c657a..90b4ee8 100644 --- a/README.md +++ b/README.md @@ -259,7 +259,7 @@ In place of a version pointer like "0.10" or "5.0" or "4.2.1", you can use the f ### Long-term support -Node has a [schedule](https://github.com/nodejs/LTS#lts_schedule) for long-term support (LTS) You can reference LTS versions in aliases and `.nvmrc` files with the notation `lts/*` for the latest LTS, and `lts/argon` for LTS releases from the "argon" line, for example. In addition, the following commands support LTS arguments: +Node has a [schedule](https://github.com/nodejs/Release#release-schedule) for long-term support (LTS) You can reference LTS versions in aliases and `.nvmrc` files with the notation `lts/*` for the latest LTS, and `lts/argon` for LTS releases from the "argon" line, for example. In addition, the following commands support LTS arguments: - `nvm install --lts` / `nvm install --lts=argon` / `nvm install 'lts/*'` / `nvm install lts/argon` - `nvm uninstall --lts` / `nvm uninstall --lts=argon` / `nvm uninstall 'lts/*'` / `nvm uninstall lts/argon`