AleksanderBodurri 445fbf81fd refactor(devtools): bring the angular devtools directory into the root bazel workspace ... Previously devtools used a nested workspace for its bazel configurations. This meant framework dependencies were consumed via npm. Now devtools is part of the root bazel directory that all other files in this codebase fall under. This allows us to build devtools using local angular packages, removing the need to consume these dependencies with npn. This is useful because we no longer have to update these dependencies with an automated tool like renovate, and our CI tests will always run against the most up to date framework packages.		2022-01-26 16:35:31 -05:00
..
demo-no-zone	refactor(devtools): bring the angular devtools directory into the root bazel workspace	2022-01-26 16:35:31 -05:00
ng-devtools	refactor(devtools): bring the angular devtools directory into the root bazel workspace	2022-01-26 16:35:31 -05:00
ng-devtools-backend	refactor(devtools): bring the angular devtools directory into the root bazel workspace	2022-01-26 16:35:31 -05:00
protocol	refactor(devtools): bring the angular devtools directory into the root bazel workspace	2022-01-26 16:35:31 -05:00
shared-utils	refactor(devtools): bring the angular devtools directory into the root bazel workspace	2022-01-26 16:35:31 -05:00
shell-chrome	refactor(devtools): bring the angular devtools directory into the root bazel workspace	2022-01-26 16:35:31 -05:00