third_party/WebKit/Source/devtools/readme.md - Issue 2669593003: DevTools: npm test - add --target=SUB_DIRECTORY_NAME

Side by Side Diff: third_party/WebKit/Source/devtools/readme.md

Issue 2669593003: DevTools: npm test - add --target=SUB_DIRECTORY_NAME (Closed)

Patch Set: fix readme Created 3 years, 10 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

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

(...skipping 82 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
93 > Tip: [Learn about the test harness flags](https://chromium.googlesource.co m/chromium/src/+/master/docs/testing/layout_tests.md#Test-Harness-Options)	93 > Tip: [Learn about the test harness flags](https://chromium.googlesource.co m/chromium/src/+/master/docs/testing/layout_tests.md#Test-Harness-Options)

94	94

95 #### `--fetch-content-shell`	95 #### `--fetch-content-shell`

96 ```	96 ```

97 # If you're using a full chromium checkout and have a compiled content shell,	97 # If you're using a full chromium checkout and have a compiled content shell,

98 # this will fetch a pre-compiled content shell. This is useful if you	98 # this will fetch a pre-compiled content shell. This is useful if you

99 # haven't compiled your content shell recently	99 # haven't compiled your content shell recently

100 npm test -- --fetch-content-shell	100 npm test -- --fetch-content-shell

101 ```	101 ```

102	102

	103 #### `--target=SUB_DIRECTORY_NAME`

	104 ```

	105 # If you're using a build sub-directory that's not out/Release,

	106 # such as out/Default, then use --target=SUB_DIRECTORY_NAME

	107 npm test -- --target=Default

	108 ```

103 ### Development	109 ### Development

104 * All devtools commits: [View the log], [RSS feed] or [@DevToolsCommits] on Twit ter	110 * All devtools commits: [View the log], [RSS feed] or [@DevToolsCommits] on Twit ter

105 * [All open DevTools tickets] on crbug.com	111 * [All open DevTools tickets] on crbug.com

106 * File a new DevTools ticket: [new.crbug.com](https://bugs.chromium.org/p/chromi um/issues/entry?labels=OS-All,Type-Bug,Pri-2&components=Platform%3EDevTools)	112 * File a new DevTools ticket: [new.crbug.com](https://bugs.chromium.org/p/chromi um/issues/entry?labels=OS-All,Type-Bug,Pri-2&components=Platform%3EDevTools)

107 * Code reviews mailing list: [devtools-reviews@chromium.org]	113 * Code reviews mailing list: [devtools-reviews@chromium.org]

108	114

109 ### Getting in touch	115 ### Getting in touch

110 * [@ChromeDevTools] on Twitter	116 * [@ChromeDevTools] on Twitter

111 * Chrome DevTools mailing list: [groups.google.com/forum/google-chrome-developer -tools](https://groups.google.com/forum/#!forum/google-chrome-developer-tools)	117 * Chrome DevTools mailing list: [groups.google.com/forum/google-chrome-developer -tools](https://groups.google.com/forum/#!forum/google-chrome-developer-tools)

112	118

113 [devtools-reviews@chromium.org]: https://groups.google.com/a/chromium.org/foru m/#!forum/devtools-reviews	119 [devtools-reviews@chromium.org]: https://groups.google.com/a/chromium.org/foru m/#!forum/devtools-reviews

114 [RSS feed]: https://feeds.peter.sh/chrome-devtools/	120 [RSS feed]: https://feeds.peter.sh/chrome-devtools/

115 [View the log]: https://chromium.googlesource.com/chromium/src/third_party/Web Kit/Source/devtools/+log/master	121 [View the log]: https://chromium.googlesource.com/chromium/src/third_party/Web Kit/Source/devtools/+log/master

116 [@ChromeDevTools]: http://twitter.com/ChromeDevTools	122 [@ChromeDevTools]: http://twitter.com/ChromeDevTools

117 [@DevToolsCommits]: http://twitter.com/DevToolsCommits	123 [@DevToolsCommits]: http://twitter.com/DevToolsCommits

118 [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	124 [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

« no previous file with comments | « no previous file | third_party/WebKit/Source/devtools/scripts/npm_test.js » ('j') | no next file with comments »