From 27378842411ea6aabfac8ababbf53fb0d73eeadb Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mladen=20Mihajlovi=C4=87?= Date: Tue, 21 May 2019 08:39:47 +0200 Subject: [PATCH] Updated readme with info gathered from issues Specifically https://github.com/microsoft/vscode-recipes/issues/201#issuecomment-473353746 Also warning removed since that issue was resolved as a babel issue... --- vuejs-cli/README.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/vuejs-cli/README.md b/vuejs-cli/README.md index ef4a349..f277aff 100644 --- a/vuejs-cli/README.md +++ b/vuejs-cli/README.md @@ -4,8 +4,6 @@ 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). -**Notice**: Please be aware that we have found issues with the sourcemaps generated by vue-cli, which are causing problems for the debugging experience in VS Code. See https://github.com/vuejs/vue-loader/issues/1163 - 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 @@ -80,7 +78,10 @@ Then click on the gear icon to configure a launch.json file, selecting **Chrome* "webRoot": "${workspaceFolder}/src", "breakOnLoad": true, "sourceMapPathOverrides": { - "webpack:///./src/*": "${webRoot}/*" + "webpack:///./src/*": "${webRoot}/*", + "webpack:///src/*": "${webRoot}/*", + "webpack:///*": "*", + "webpack:///./~/*": "${webRoot}/node_modules/*" } } ]