From 3242baf0880d1cdc0e20b546d3c1da952e474444 Mon Sep 17 00:00:00 2001 From: Artem Varaksa Date: Mon, 16 Jul 2018 20:10:14 +0300 Subject: [PATCH] docs: update more dead links in README.md (#13) Fixes: https://npm.community/t/npm-troubleshooting-guide-link-in-readme-leads-to-404/601 PR-URL: https://github.com/npm/cli/pull/13 Credit: @u32i64 Reviewed-By: @zkat --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 87aab26d90bc4..22f046f1a85de 100644 --- a/README.md +++ b/README.md @@ -1,7 +1,7 @@ npm(1) -- a JavaScript package manager ============================== -[![Build Status](https://img.shields.io/travis/npm/npm/latest.svg)](https://travis-ci.org/npm/npm) +[![Build Status](https://img.shields.io/travis/npm/cli/latest.svg)](https://travis-ci.org/npm/cli) ## SYNOPSIS @@ -88,7 +88,7 @@ experience if you run a recent version of npm. To upgrade, either use [Microsoft upgrade tool](https://github.com/felixrieseberg/npm-windows-upgrade), [download a new version of Node](https://nodejs.org/en/download/), or follow the Windows upgrade instructions in the -[npm Troubleshooting Guide](./TROUBLESHOOTING.md). +[Installing/upgrading npm](https://npm.community/t/installing-upgrading-npm/251/2) post. If that's not fancy enough for you, then you can fetch the code with git, and mess with it directly.