Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 4 additions & 5 deletions packages/angular/cli/BUILD.bazel
Original file line number Diff line number Diff line change
Expand Up @@ -107,15 +107,14 @@ ts_project(
"node_modules/**",
],
),
# TODO: Fix strict_deps failure
ignore_strict_deps = True,
deps = [
":angular-cli_rjs",
":node_modules/@angular-devkit/core",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would we prefer to move from the ts_project dependency here to the npm package one?

Or should the clean up be to migrate to relative paths? If I understand/remember correctly, we want to use the npm package here so that we don't cross the npm package boundary with relative paths.

If there were imports from @angular/cli those should be relative import paths instead though.

Copy link
Member

@devversion devversion Feb 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This makes a lot of sense. It's just a leftover because apparently no runtime test broke (likely due to the transitive deps!!). My goal is to restrict/fix this and make it safe by leveraging Bazel visibility rules better

":node_modules/@angular-devkit/schematics",
"//:node_modules/@types/semver",
"//:node_modules/@types/yargs",
"//packages/angular_devkit/core:core_rjs",
"//packages/angular_devkit/schematics:schematics_rjs",
"//packages/angular_devkit/schematics/testing:testing_rjs",
"//:node_modules/semver",
"//:node_modules/yargs",
],
)

Expand Down
Loading