Install gulp
globally and all dependencies.
$ npm install gulp -g
$ npm install
$ webpack --progress --color --watch
Builds all webpacked projects, and
waits for changes. This is much quicker than gulp watch
because webpack
caches the parsed JS files, and only outputs the changes$ gulp build-prefs
Creates the ./build/preferences.json
file; only need
to run if client/preferences/devtools.js
changes.listen
in GCLI (uses default port 6080)gulp start
to start the proxy and static dev server.It's worth noting that the server serves everything in the devtools.html directory to localhost:8081. This is probably OK unless you either don't trust yourself, or you open the port to the network and store private files in this directory.
http://localhost:8081/?wsPort=9000
to run the connection test tool. You
should see something like this:
Success! Check console for protocol logs. TabTarget:server2.conn26.child13/tab1 [Front for inspector/server2.conn26.child13/inspectorActor3] [Front for domwalker/server2.conn26.child13/domwalker28]
And see TCP -> WS logs in the console where you ran gulp serve-connect
--remote-debugging-port=9222
CLI arg
/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --remote-debugging-port=9222
gulp start
http://localhost:8081/?wsPort=9001
to run the connection test tool, or the toolbox
at http://localhost:8081/client/framework/toolbox-wrapper.html
if
statement in getWSTarget
in client/framework/toolbox.js
to true.Initial setup:
$ git clone https://github.com/servo/servo.git
$ cd servo/
$ ./mach build -r # release build
Start servo with a devtools server listening on port 6080 and open to mozilla.org:
$ ./mach run --devtools 6080 https://google.com
See also: