build: add tsickle as explicit dependency #18116
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds tsickle as explicit dependency. This is necessary because
we access it from
node_modules/tsickle
in a Bazel target thatwraps tsc with tsickle.
In the past we just relied on the transitive dependency of
@angular/bazel
being hoisted, but the hoisting is not guaranteedif the lock file changes (e.g. when running
yarn upgrade
). In general,dependencies we explicitly access, should be added as explicit dependencies.