gecko-dev/gfx/wr/debugger
Kartikaya Gupta 5023b06a14 Bug 1542826 - Rebuild the debugger front-end. r=gw
This patch is the output of rebuilding the debugger frontend with a
recent npm installation. The changes to dist/ and the addition of
package-lock.json are a result of the build. The changes to package.json
and main.js were done manually to work around an incompatible change
in beufy 0.6.7 (the lib/ folder changed to dist/).

Differential Revision: https://phabricator.services.mozilla.com/D28357

--HG--
extra : moz-landing-system : lando
2019-04-25 19:31:09 +00:00
..
dist Bug 1542826 - Rebuild the debugger front-end. r=gw 2019-04-25 19:31:09 +00:00
src Bug 1542826 - Rebuild the debugger front-end. r=gw 2019-04-25 19:31:09 +00:00
.babelrc
.editorconfig
.gitignore
README.md
index.html
package-lock.json Bug 1542826 - Rebuild the debugger front-end. r=gw 2019-04-25 19:31:09 +00:00
package.json Bug 1542826 - Rebuild the debugger front-end. r=gw 2019-04-25 19:31:09 +00:00
webpack.config.js

README.md

WebRender Debugger

A web based debugger for WebRender.

Using the debugger

Build your application with the debugger feature enabled, for example in wrench:

cargo build --features=debugger

Now, open your browser and open the debugger/index.html file. Click Connect and the debugger will attempt to connect to WR via websocket.

Using the debugger with Gecko

In the Gecko source tree, open gfx/webrender_bindings/Cargo.toml in a text editor.

Add features = ['debugger'] to the end of the file (in the dependencies.webrender section).

Vendor the rust dependencies locally for the debugger (we don't want these committed to the repo): ./mach vendor rust

Now, build and run as usual, and the debugger will be available.