Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/ChromeDevTools/debugger-protocol-viewer
DevTools Protocol API docs—its domains, methods, and events
https://github.com/ChromeDevTools/debugger-protocol-viewer
chrome-debugging-protocol chrome-devtools
Last synced: about 1 month ago
JSON representation
DevTools Protocol API docs—its domains, methods, and events
- Host: GitHub
- URL: https://github.com/ChromeDevTools/debugger-protocol-viewer
- Owner: ChromeDevTools
- License: other
- Created: 2015-03-02T21:16:09.000Z (almost 10 years ago)
- Default Branch: master
- Last Pushed: 2024-05-01T12:34:22.000Z (8 months ago)
- Last Synced: 2024-05-02T08:10:51.473Z (7 months ago)
- Topics: chrome-debugging-protocol, chrome-devtools
- Language: JavaScript
- Homepage: https://chromedevtools.github.io/devtools-protocol/
- Size: 10.4 MB
- Stars: 852
- Watchers: 51
- Forks: 171
- Open Issues: 13
-
Metadata Files:
- Readme: readme.md
- License: LICENSE
Awesome Lists containing this project
- awesome-starred-test - ChromeDevTools/debugger-protocol-viewer - DevTools Protocol API docs—its domains, methods, and events (JavaScript)
- awesome-hacking-lists - ChromeDevTools/debugger-protocol-viewer - DevTools Protocol API docs—its domains, methods, and events (JavaScript)
README
# devtools-protocol
Explore the Chrome DevTools Protocol, its methods, events and basic documentation.
More: [DevTools Protocol repo](https://github.com/ChromeDevTools/devtools-protocol) and [published devtools protocol viewer](https://chromedevtools.github.io/devtools-protocol/)
## Building
```sh
# install dependencies
npm i
# regenerate the protocol files
npm run prep
# build it
npm run build
# serve it locally
npm run serve
```
## Deploying
We deploy to https://chromedevtools.github.io/devtools-protocol/ despite the source living here.
The [repo/branch layout is described here](https://github.com/ChromeDevTools/debugger-protocol-viewer/issues/78).
There is no need to manually trigger deployments. It’s done [automatically](https://github.com/ChromeDevTools/devtools-protocol/commit/c9c207e583264058326792210d1b29a95109beac) as part of the devtools-protocol GitHub Actions workflow.
FYI: The protocol files here in `debugger-protocol-viewer#master` don't get updated. A deployment writes to the `devtools-protocol#ghpages` branch.
## Adding new version
To add a new protocol version:
1. Modify `pages/_data/versions.json`
1. Create `pages/_data/VERSION_SLUG.json`
1. Create `_versions/VERSION_SLUG.html` file with protocol version description
1. Update the `
` tag in `pages/_includes/shell.hbs`.
1. Build project
## Adding new domains
Run `npm run prep` then `node generate-sidenav-html.js` and add into `
` in `pages/_includes/shell.hbs`.
## History
* [v0.1](https://rawgit.com/ChromeDevTools/devtools-protocol/v0.1/index.html) original Eric Guzman app.
* [v0.2](https://rawgit.com/ChromeDevTools/devtools-protocol/v0.2/index.html) irish's "upgrades".
* [v0.8](https://rawgit.com/ChromeDevTools/devtools-protocol/v0.8/index.html) guzman's polymer 0.8 refactor
* [v1.0](https://rawgit.com/ChromeDevTools/devtools-protocol/v1.0/index.html) konrad's polymer 1.0 + jekyll refactor
* [v2.0](https://github.com/ChromeDevTools/debugger-protocol-viewer/tree/polymer) tim's polymer 2.0 - jekyll refactor
* [v3.0](https://chromedevtools.github.io/devtools-protocol/) tim's Eleventy refactor
* which brings us to… [now](https://chromedevtools.github.io/devtools-protocol/).
## License
Apache
## Contributing
Pull requests very welcome!