Files

T

Ben Konyi d7cef28bee [ Observatory ] Create fork of runtime/observatory at pkg/observatory

This change further prepares for the removal of Observatory from the
shipped Dart SDK by creating a fork to be used by the remaining
Observatory users.

This is basically a straight copy of the contents from
runtime/observatory with the exception of two new scripts:

- `bin/observatory.dart`, a utility to launch Observatory
- `bin/activate.dart`, which globally activates `bin/observatory.dart`
  as `observatory`

This change also updates the presubmits to ensure that
`runtime/observatory` is effectively placed in read-only mode to prevent
any divergences with the fork.

Work towards https://github.com/dart-lang/sdk/issues/50233

Change-Id: Iff3a7512058f36afa2a96d45d94a1dff424401d6
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/429800
Reviewed-by: Siva Annamalai <asiva@google.com>
Commit-Queue: Ben Konyi <bkonyi@google.com>

2025-05-22 07:19:03 -07:00

1.4 KiB

Raw Blame History

Observatory Developer Tooling

WARNING: This tooling is deprecated and maintained on a best-effort basis by members of the Dart VM team.

Activating Observatory

To easily serve Observatory without having to manually run webdev serve in this project, Observatory can be activated as a global pub package and run via the observatory tool.

To do this, run dart bin/activate.dart, which will create the observatory script at $PUB_CACHE/bin.

Note: If any changes are made to bin/observatory.dart, dart bin/activate.dart must be re-run to pick up the changes.

Serving Observatory

To serve Observatory, simply run the observatory command. To automatically launch Observatory in Chrome, provide the --launch flag.

Developing Observatory

When making changes to Observatory, run observatory --debug to run Observatory with DDC. This will allow for a more typical web development workflow as changes to the Observatory sources will be picked up automatically on a page refresh.

Code Reviews

The development workflow of Dart (and Observatory) is based on code reviews.

Follow the code review instructions to be able to successfully submit your code.

The main reviewers for Observatory related CLs are:

aam
rmacnak

1.4 KiB Raw Blame History