| OLD | NEW |
| 1 # Chrome DevTools frontend | 1 # Chrome DevTools frontend |
| 2 | 2 |
| 3 The client-side of the Chrome DevTools, including all JS & CSS to run the DevToo
ls webapp. | 3 The client-side of the Chrome DevTools, including all JS & CSS to run the DevToo
ls webapp. |
| 4 | 4 |
| 5 It is available on NPM as the [chrome-devtools-frontend](https://www.npmjs.com/p
ackage/chrome-devtools-frontend) package. It's not currently available via CJS o
r ES2015 modules, so consuming this package in other tools may require [some eff
ort](https://github.com/paulirish/devtools-timeline-model/blob/master/index.js). | 5 It is available on NPM as the [chrome-devtools-frontend](https://www.npmjs.com/p
ackage/chrome-devtools-frontend) package. It's not currently available via CJS o
r ES2015 modules, so consuming this package in other tools may require [some eff
ort](https://github.com/paulirish/devtools-timeline-model/blob/master/index.js). |
| 6 | 6 |
| 7 #### Package versioning | 7 #### Package versioning |
| 8 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 Chro
mium commit, however the package is updated roughly daily. | 8 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 Chro
mium commit, however the package is updated roughly daily. |
| 9 | 9 |
| 10 ### Source code | 10 ### Source code |
| 11 The frontend is available through a git subtree mirror on [chromium.googlesource
.com](https://chromium.googlesource.com/chromium/src/third_party/WebKit/Source/d
evtools/), with a regularly updating GitHub mirror at [github.com/ChromeDevTools
/devtools-frontend](https://github.com/ChromeDevTools/devtools-frontend). The co
debase's true location is in `third_party/WebKit/Source/devtools/` in [Chromium'
s git repo](https://chromium.googlesource.com/chromium/src/). | 11 The frontend is available through a git subtree mirror on [chromium.googlesource
.com](https://chromium.googlesource.com/chromium/src/third_party/WebKit/Source/d
evtools/), with a regularly updating GitHub mirror at [github.com/ChromeDevTools
/devtools-frontend](https://github.com/ChromeDevTools/devtools-frontend). The co
debase's true location is in `third_party/WebKit/Source/devtools/` in [Chromium'
s git repo](https://chromium.googlesource.com/chromium/src/). |
| 12 | 12 |
| 13 ### Getting Started | 13 ### Getting Started |
| 14 | 14 |
| 15 1. Clone the repo | 15 1. Clone the repo |
| 16 2. Go to repo root and run: `npm start` | 16 2. Go to repo root and run: `npm start` |
| 17 - This launches Chrome Canary and starts the dev server with 1 command | 17 - This launches Chrome Canary and starts the dev server with 1 command |
| 18 3. Go to http://localhost:8090 | 18 3. Go to http://localhost:9222#custom=true&experiments=true |
| 19 | 19 |
| 20 > **Power user tips:** | 20 > **Power user tips:** |
| 21 > | 21 > |
| 22 > You can customize the port for the dev server: e.g. `PORT=8888 npm start`. | 22 > You can customize the port for the dev server: e.g. `PORT=8888 npm start`. |
| 23 > | 23 > |
| 24 > You can also launch chrome and start the server separately: | 24 > You can also launch chrome and start the server separately: |
| 25 > - `npm run chrome` | 25 > - `npm run chrome` |
| 26 > - `npm run server` | 26 > - `npm run server` |
| 27 > | 27 > |
| 28 > When you start Chrome separately, you can pass extra args to Chrome: | 28 > When you start Chrome separately, you can pass extra args to Chrome: |
| (...skipping 32 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 61 ### Getting in touch | 61 ### Getting in touch |
| 62 * [@ChromeDevTools] on Twitter | 62 * [@ChromeDevTools] on Twitter |
| 63 * Chrome DevTools mailing list: [groups.google.com/forum/google-chrome-developer
-tools](https://groups.google.com/forum/#!forum/google-chrome-developer-tools) | 63 * Chrome DevTools mailing list: [groups.google.com/forum/google-chrome-developer
-tools](https://groups.google.com/forum/#!forum/google-chrome-developer-tools) |
| 64 | 64 |
| 65 [devtools-reviews@chromium.org]: https://groups.google.com/a/chromium.org/foru
m/#!forum/devtools-reviews | 65 [devtools-reviews@chromium.org]: https://groups.google.com/a/chromium.org/foru
m/#!forum/devtools-reviews |
| 66 [RSS feed]: https://feeds.peter.sh/chrome-devtools/ | 66 [RSS feed]: https://feeds.peter.sh/chrome-devtools/ |
| 67 [View the log]: https://chromium.googlesource.com/chromium/src/third_party/Web
Kit/Source/devtools/+log/master | 67 [View the log]: https://chromium.googlesource.com/chromium/src/third_party/Web
Kit/Source/devtools/+log/master |
| 68 [@ChromeDevTools]: http://twitter.com/ChromeDevTools | 68 [@ChromeDevTools]: http://twitter.com/ChromeDevTools |
| 69 [@DevToolsCommits]: http://twitter.com/DevToolsCommits | 69 [@DevToolsCommits]: http://twitter.com/DevToolsCommits |
| 70 [all open DevTools tickets]: https://bugs.chromium.org/p/chromium/issues/list?
can=2&q=component%3APlatform%3EDevTools&sort=&groupby=&colspec=ID+Stars+Owner+Su
mmary+Modified+Opened | 70 [all open DevTools tickets]: https://bugs.chromium.org/p/chromium/issues/list?
can=2&q=component%3APlatform%3EDevTools&sort=&groupby=&colspec=ID+Stars+Owner+Su
mmary+Modified+Opened |
| OLD | NEW |