chore: remove mention of the chrome debugger

connor4312 · connor4312 · commit 8a2465fa54ad · 2021-10-18T09:48:16.000-07:00
diff --git a/Angular-SpaTemplates/README.md b/Angular-SpaTemplates/README.md
@@ -2,14 +2,12 @@
 
 by [John Pankowicz](https://github.com/johnpankowicz)
 
-This recipe shows how to use both the [Debugger for Chrome](https://github.com/Microsoft/vscode-chrome-debug) extension and the [C# for Visual Studio Code](https://github.com/OmniSharp/omnisharp-vscode) extension together to debug a C#/Typescript application generated by the [Angular AspNetCore.SpaTemplates](https://www.nuget.org/packages/Microsoft.AspNetCore.SpaTemplates/).
+This recipe shows how to use both the built-in JavaScript debugger and the [C# for Visual Studio Code](https://github.com/OmniSharp/omnisharp-vscode) extension together to debug a C#/Typescript application generated by the [Angular AspNetCore.SpaTemplates](https://www.nuget.org/packages/Microsoft.AspNetCore.SpaTemplates/).
 
 ## Prerequisites to install
 
 - [Google Chrome](https://www.google.com/chrome) installed in its default location.
 
-- Version **3.5.0** or greater of the [Debugger for Chrome](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome) extension installed in VS Code.
-
 - Version **1.13.1** of the [C# for Visual Studio Code](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.csharp) extension installed in VS Code.
 
 - .NET Core SDK 1.0 RC4 (or later) for Windows, Mac, or Linux
diff --git a/Electron/README.md b/Electron/README.md
@@ -2,19 +2,17 @@
 
 By [Kenneth Auchenberg](https://twitter.com/auchenberg)
 
-This recipe shows how to use the built-in Node Debugger and the [Debugger for Chrome](https://github.com/Microsoft/vscode-chrome-debug) extension with VS Code to debug [Electron](https://electron.atom.io) applications.
+This recipe shows how to use the built-in JavaScript deubgger in VS Code to debug [Electron](https://electron.atom.io) applications.
 
-[Electron](https://electron.atom.io) applications can consist of two process types: a main process type running in NodeJS, and a renderer process type in Chromium. This means that you'll need to use two debugger instances within VS Code to debug both processes. This is the reason you'll need both the built-in Node Debugger and the [Debugger for Chrome](https://github.com/Microsoft/vscode-chrome-debug) extension.
+[Electron](https://electron.atom.io) applications can consist of two process types: a main process type running in NodeJS, and a renderer process type in Chromium. This means that you'll need to use two debugger instances within VS Code to debug both processes.
 
 **Note:** Please make sure you are using **Electron 1.7.4 or newer**, as our debuggers rely on the inspector protocol.
 
 ## Getting Started
 
 1. Make sure you're running the latest version of VS Code.
 
-2. Also make sure the latest version of the [Debugger for Chrome](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome) extension is installed in VS Code.
-
-3. This guide assumes that you are using the [electron-quick-start project](https://github.com/electron/electron-quick-start). Clone the repo to get started:
+2. This guide assumes that you are using the [electron-quick-start project](https://github.com/electron/electron-quick-start). Clone the repo to get started:
     >
     ```
     git clone https://github.com/electron/electron-quick-start.git
diff --git a/Next-js/README.md b/Next-js/README.md
@@ -2,19 +2,17 @@
 
 By [Kenneth Auchenberg](https://twitter.com/auchenberg)
 
-This recipe shows how to use the built-in Node Debugger and the [Debugger for Chrome](https://github.com/Microsoft/vscode-chrome-debug) extension with VS Code to debug [next.js](https://github.com/zeit/next.js) applications.
+This recipe shows how to use the built-in JavaScript deubgger in VS Code to debug [next.js](https://github.com/zeit/next.js) applications.
 
-Next.js allows ReactJS to be used both on the server and client, which is a great match for VS Code, as we can debug both the server and client at the same time! This means that you'll need to use two debugger instances within VS Code to debug both ends. This is the reason for why you'll need both the built-in Node Debugger and the [Debugger for Chrome](https://github.com/Microsoft/vscode-chrome-debug).
+Next.js allows ReactJS to be used both on the server and client, which is a great match for VS Code, as we can debug both the server and client at the same time! This means that you'll need to use two debugger instances within VS Code to debug both ends.
 
 **Note:** Please make sure you are using **Next.js 4.2.0-canary.1 or newer**, as our debuggers relies on source maps, and there's been a bunch of improvements for this in next.js.
 
 ## Getting Started
 
 1. Make sure to have the latest version of VS Code installed.
 
-2. Make sure to the latest version of [Debugger for Chrome](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome) extension installed in VS Code.
-
-3. This guide assumes that you are using the official sample app [nextgram](https://github.com/zeit/nextgram). Clone the repo to get started:
+2. This guide assumes that you are using the official sample app [nextgram](https://github.com/zeit/nextgram). Clone the repo to get started:
     >
     ```
     git clone git@github.com:now-examples/nextgram.git
diff --git a/meteor/README.md b/meteor/README.md
@@ -2,19 +2,17 @@
 
 by [Kenneth Auchenberg](https://twitter.com/auchenberg)
 
-This recipe shows how to use the built-in Node Debugger and the [Debugger for Chrome](https://github.com/Microsoft/vscode-chrome-debug) extension with VS Code to debug [meteor](https://www.meteor.com/) applications.
+This recipe shows how to use the built-in JavaScript deubgger in VS Code to debug [meteor](https://www.meteor.com/) applications.
 
-Meteor is used to write applications that run on both the server and client with the same code, and this is a great match for VS Code, as we can debug both the server and client at the same time! This means that you'll need to use two debugger instances within VS Code to debug both ends. This is the reason for why you'll need both the built-in Node Debugger and the [Debugger for Chrome](https://github.com/Microsoft/vscode-chrome-debug).
+Meteor is used to write applications that run on both the server and client with the same code, and this is a great match for VS Code, as we can debug both the server and client at the same time! This means that you'll need to use two debugger instances within VS Code to debug both ends.
 
 **Note:** Please make sure you are using **Meteor 1.6+ and Node.js 8.9+**, as our debuggers rely on the new Inspector protocol, which landed in [Meteor PR9201](https://github.com/meteor/meteor/pull/9201)
 
 ## Getting Started
 
 1. Make sure to have the latest version of VS Code installed.
 
-2. Make sure to have the latest version of [Debugger for Chrome](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome) extension installed in VS Code.
-
-3. This guide assumes that you are using the official sample app [simple-todos-react](https://github.com/meteor/simple-todos-react). Clone the repo to get started:
+2. This guide assumes that you are using the official sample app [simple-todos-react](https://github.com/meteor/simple-todos-react). Clone the repo to get started:
     >
     ```
     git clone https://github.com/meteor/simple-todos-react
diff --git a/vuejs-cli/README.md b/vuejs-cli/README.md
@@ -2,31 +2,29 @@
 
 by [Kenneth Auchenberg](https://twitter.com/auchenberg)
 
-This recipe shows how to use the [Debugger for Chrome](https://github.com/Microsoft/vscode-chrome-debug) extension with VS Code to debug Vue.js applications generated by the [Vue CLI](https://github.com/vuejs/vue-cli).
+This recipe shows how to use the built-in JavaScript deubgger in VS Code to debug Vue.js applications generated by the [Vue CLI](https://github.com/vuejs/vue-cli).
 
 If you're using Vue.js through the Nuxt.js framework, see https://codeburst.io/debugging-nuxt-js-with-visual-studio-code-724920140b8f
 
 ## Getting Started
 
 1. Make sure to have [Google Chrome](https://www.google.com/chrome) installed in its default location.
 
-2. Make sure to the latest version of [Debugger for Chrome](https://marketplace.visualstudio.com/items?itemName=msjsdiag.debugger-for-chrome) extension installed in VS Code.
-
-3. Use [NPM](https://www.npmjs.com) to install [vue-cli](https://github.com/vuejs/vue-cli)
+2. Use [NPM](https://www.npmjs.com) to install [vue-cli](https://github.com/vuejs/vue-cli)
 
    ```
    npm install -g @vue/cli
    ```
 
-4. Use Vue CLI to create a new Vue.js app.
+3. Use Vue CLI to create a new Vue.js app.
 
    ```
    vue create hello-world
    ```
 
    You will be prompted to pick a preset. You can either choose the default preset which comes with a basic Babel + ESLint setup,or select "Manually select features" to pick the features you need.
 
-5. Change to the newly created application directory and open VS Code.
+4. Change to the newly created application directory and open VS Code.
 
    ```
    cd hello-world
