Skip to content
Branch: master
Clone or download
Pull request Compare This branch is 43 commits ahead, 421 commits behind ChromeDevTools:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
front_end ddt - Sort .dart files before others in file selection (#67) Apr 25, 2019
lib Evaluate Dart expressions by sending them to the server for compilati… Jan 10, 2019
scripts Merging from chrome-devtools, fixing conflicts Dec 22, 2018
services The Great Blink mv for source files, part 2. Apr 7, 2018
.clang-format The Great Blink mv for source files, part 2. Apr 7, 2018
.eslintignore DevTools: Argument hints for native functions May 14, 2018
.eslintrc.js The Great Blink mv for source files, part 2. Apr 7, 2018
.gitignore [ddt] Re-apply all the DDT changes to date Dec 22, 2018
.npmignore The Great Blink mv for source files, part 2. Apr 7, 2018
.style.yapf The Great Blink mv for source files, part 2. Apr 7, 2018
BUILD.gn DevTools: Code Folding Dec 15, 2018
CHANGELOG.md ddt - Try 'main' as a function name if we aren't given one (#62) Mar 13, 2019
DART_UPDATE_NOTES.md [ddt] Update Devtools protocol files (#51) Feb 6, 2019
LICENSE
OWNERS.chromium Actually add the renamed OWNERS files (#35) Dec 22, 2018
PRESUBMIT.py DevTools: fix DevTools docs after blink rename Apr 9, 2018
build.yaml Evaluate Dart expressions by sending them to the server for compilati… Jan 10, 2019
ddt [ddt] Re-apply all the DDT changes to date Dec 22, 2018
debug_tests.sh Evaluate Dart expressions by sending them to the server for compilati… Jan 10, 2019
htaccess Layout tests should not rely on file URL's universal access on CORS Sep 19, 2018
package.json [ddt] Re-apply all the DDT changes to date Dec 22, 2018
protocol.json
pubspec.yaml Evaluate Dart expressions by sending them to the server for compilati… Jan 10, 2019
readme.md Update readme.md Apr 1, 2019
run_tests.sh Add basic infrastructure for running Dart tests Dec 22, 2018
test Add basic infrastructure for running Dart tests Dec 22, 2018

readme.md

Dart support for Chrome DevTools

This is a fork of the client-side of the Chrome DevTools, including all JS & CSS to run the DevTools webapp. The original sources are at https://github.com/ChromeDevTools

Getting Started

  1. Make sure you have npm installed. https://nodejs.org/en/ - Google internal users, see go/nodejs-install
  2. Clone the repo - git clone https://github.com/dart-lang/devtools-frontend.git
  3. Go to repo root and run: npm install
  4. From the same directory, run ./ddt <url>
    • This launches a separate instance of Chrome in a new user profile with the debugging port open and also starts the devtools server.
    • If CHROMIUM_PATH is set (e.g. export CHROMIUM_PATH=<path to chrome executable>) then it will use that version of Chrome. Otherwise, it will default to either chrome or google-chrome if either of those is found in the PATH.
    • It should automatically open three pages, a reference page, the web app at and a Dart DevTools instance on that page.

Power user tips:

You can run chrome and the server directly by running npm start. This enables customizing the options. For example, you can customize the port for the dev server: e.g. PORT=8888 npm start.

You can also launch chrome and start the server separately:

  • npm run chrome
  • npm run server

When you start Chrome separately, you can pass extra args to Chrome:

npm run chrome -- https://news.ycombinator.com

(e.g. this launches Hacker News on startup)

If you want to reset your development profile for Chrome, pass in "--reset-profile":

npm start -- --reset-profile

OR

npm run chrome -- --reset-profile

Changes from Regular Devtools

  • Custom formatters are on by default
  • Black boxing the SDK is on by default
  • A minimal set of Dart expressions work in the console and watch. Only expression of the form "object.thing.otherThing" work so far, and some object references won't work (e.g. library variables).
  • A fix for one of the breakpoint location problems
  • (This has been temporarily reverted, until the SDK with the fixes for custom formatter colors is released) The dark theme is used by default, to visually distinguish it from normal devtools. It can be changed back in devtools settings.
  • Added keyboard shortcuts Alt-R for hot-restart, and Alt-S to toggle source maps.
  • If it detects a breakpoint that doesn't get set where you clicked, you'll get a description on the console saying so and indicating where to file a bug.
  • Inline values displayed in the source pane use the custom formatters, rather than displaying with very long class names.

Bugs

  • File issues against this repo, https://github.com/dart-lang/devtools-frontend/issues , unless they contain confidential information, in which case they can be filed against the "Dev Compiler (DDC)" component.
You can’t perform that action at this time.