DevTools: improve launch chrome (add --reset-profile option)

third_party/WebKit/Source/devtools/readme.md

 # Chrome DevTools frontend
 
 The client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp.
 
 It is available on NPM as the [chrome-devtools-frontend](https://www.npmjs.com/package/chrome-devtools-frontend) package. It's not currently available via CJS or ES2015 modules, so consuming this package in other tools may require [some effort](https://github.com/paulirish/devtools-timeline-model/blob/master/index.js).
 
 #### Package versioning
 The version number of the npm package (e.g. `1.0.373466`) refers to the Chromium commit position of latest frontend git commit. It's incremented with every Chromium commit, however the package is updated roughly daily.
 
 ### Source code
@@ skipping 12 matching lines @@
 >
 > You can also launch chrome and start the server separately:
 > - `npm run chrome`
 > - `npm run server`
 >
 > When you start Chrome separately, you can pass extra args to Chrome:
 > ```
 > npm run chrome -- https://news.ycombinator.com
 > ```
 > (e.g. this launches Hacker News on startup)
+>
+> If you want to reset your development profile for Chrome, pass in "--reset-profile":
+> ```
+> npm start -- --reset-profile
+> ```
+> *OR*
+> ```
+> npm run chrome -- --reset-profile

[dgozman, 2016/11/09 23:34:39]

Why extra -- ? This looks like a flag of the "run" command for me, not like a
chrome flag.

[chenwilliam, 2016/11/09 23:48:20]

I see what you're saying. Unfortunately, it's an npm configuration where only
the args after "--" are passed to the node.js script [0]. Thus, with these npm
commands, I can't do "npm run chrome --reset-profile" even though that looks
cleaner.

[0] https://docs.npmjs.com/cli/run-script

+> ```
 
 ### Hacking
 * DevTools documentation: [devtools.chrome.com](https://devtools.chrome.com)
 * [Debugging protocol docs](https://developer.chrome.com/devtools/docs/debugger-protocol) and [Chrome Debugging Protocol Viewer](http://chromedevtools.github.io/debugger-protocol-viewer/)
 * [awesome-chrome-devtools](https://github.com/paulirish/awesome-chrome-devtools): recommended tools and resources
 * Contributing to DevTools: [bit.ly/devtools-contribution-guide](http://bit.ly/devtools-contribution-guide)
 
 ### Useful Commands
 
 Basic:
@@ skipping 19 matching lines @@
 ### Getting in touch
 * [@ChromeDevTools] on Twitter
 * Chrome DevTools mailing list: [groups.google.com/forum/google-chrome-developer-tools](https://groups.google.com/forum/#!forum/google-chrome-developer-tools)
 
   [devtools-reviews@chromium.org]: https://groups.google.com/a/chromium.org/forum/#!forum/devtools-reviews
   [RSS feed]: https://feeds.peter.sh/chrome-devtools/
   [View the log]: https://chromium.googlesource.com/chromium/src/third_party/WebKit/Source/devtools/+log/master
   [@ChromeDevTools]: http://twitter.com/ChromeDevTools
   [@DevToolsCommits]: http://twitter.com/DevToolsCommits
   [all open DevTools tickets]: https://bugs.chromium.org/p/chromium/issues/list?can=2&q=component%3APlatform%3EDevTools&sort=&groupby=&colspec=ID+Stars+Owner+Summary+Modified+Opened