From 4f7a86aa3f804f717de8d650c34af4517361e80e Mon Sep 17 00:00:00 2001 From: Daijiro Wachi Date: Wed, 18 Jul 2018 10:12:03 +0900 Subject: [PATCH] docs: replace troubleshooting.md with posts Refs: https://github.com/npm/cli/pull/5 --- CONTRIBUTING.md | 2 +- README.md | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index f412dc93ed82b..3fc4ff5dc7a82 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -35,7 +35,7 @@ This includes anyone who may show up to the npm/npm repo with issues, PRs, comme * Comment on issues when they have a reference to the answer. * If community members aren't sure they are correct and don't have a reference to the answer, please leave the issue and try another one. * Defer to collaborators and npm employees for answers. -* Make sure to search for [the troubleshooting doc](./TROUBLESHOOTING.md) and search on the issue tracker for similar issues before opening a new one. +* Make sure to search for [the troubleshooting posts on npm.community](https://npm.community/c/support/troubleshooting) and search on the issue tracker for similar issues before opening a new one. * Any users with urgent support needs are welcome to email support@npmjs.com, and our dedicated support team will be happy to help. PLEASE don't @ collaborators or npm employees on issues. The CLI team is small, and has many outstanding commitments to fulfill. diff --git a/README.md b/README.md index 87aab26d90bc4..0124336465289 100644 --- a/README.md +++ b/README.md @@ -87,8 +87,7 @@ Many improvements for Windows users have been made in npm 3 - you will have a be experience if you run a recent version of npm. To upgrade, either use [Microsoft's 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). +or follow the Windows upgrade instructions in [the troubleshooting posts on npm.community](https://npm.community/c/support/troubleshooting). If that's not fancy enough for you, then you can fetch the code with git, and mess with it directly.