angular/devtools/tools
Doug Parker 384341d900 feat(devtools): deploy source maps
This adds source maps to both the dev and production builds. Since this project is open source and downloaded ahead of time, there is not much negative cost to shipping source maps in production, as this can help any developers who encounter bugs related to Angular DevTools on the page.

There is a slight performance cost to both processing the `sourceMappingURL` comment _and_ actually processing the sourcemaps. Ideally, we would use linked sourcemaps all the time, as this avoids processing this and parses only a trivial comment unless the user actually opens a debugger. Unfortunately, Chrome seems to fail to load linked sourcemaps for scripts injected into the user's page (the backend script and content scripts), so these need inlined sourcemaps to work, which somewhat increases the performance cost. These scripts should be small enough to not be a major issue, but we can consider removing them in production based on signal from the community if necessary.
2026-02-24 09:28:05 -08:00
..
angular-optimization docs: replace old https://angular.io/license with https://angular.dev/license 2026-01-12 13:41:30 -08:00
esbuild build: remove ts_project_interop infrastructure (#62908) 2025-07-31 09:12:58 +00:00
BUILD.bazel build: migrate devtools to use packaged version of @angular/* packages (#62413) 2025-07-02 16:10:25 +00:00
defaults.bzl feat(devtools): deploy source maps 2026-02-24 09:28:05 -08:00
release.mts refactor(devtools): make release script compatible with type stripping 2026-01-07 14:28:17 -08:00