Updated readme with info gathered from issues

Specifically microsoft#201 (comment)

Also warning removed since that issue was resolved as a babel issue...

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/*"
       }
     }
   ]