Skip to content

build: add tsickle as explicit dependency #18116

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

devversion
Copy link
Member

Adds tsickle as explicit dependency. This is necessary because
we access it from node_modules/tsickle in a Bazel target that
wraps tsc with tsickle.

In the past we just relied on the transitive dependency of
@angular/bazel being hoisted, but the hoisting is not guaranteed
if the lock file changes (e.g. when running yarn upgrade). In general,
dependencies we explicitly access, should be added as explicit dependencies.

Adds tsickle as explicit dependency. This is necessary
because we access it from `node_modules/tsickle` in a
Bazel target that wraps tsc with tsickle.

In the past we just relied on the transitive dependency
of `@angular/bazel` being hoisted, but the hoisting is
not guaranteed if the lock file changes (e.g. when running `yarn
upgrade`). In general, dependencies we explicitly access, should be
added as explicit dependencies.
@devversion devversion added pr: merge safe target: patch This PR is targeted for the next patch release labels Jan 6, 2020
@devversion devversion requested review from jelbourn and a team as code owners January 6, 2020 21:02
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Jan 6, 2020
Copy link
Member

@crisbeto crisbeto left a comment

Choose a reason for hiding this comment

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

Shouldn't the lock file be updated as well?

@devversion
Copy link
Member Author

@crisbeto The lock file doesn't change. This is a pure package.json change that ensures that tsickle is hoisted in node_modules. The lock file doesn't update as the version range already matches the version range of tsickle brought in by @angular/bazel.

tsickle@^0.37.1:

Copy link
Contributor

@Splaktar Splaktar left a comment

Choose a reason for hiding this comment

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

LGTM

@devversion devversion added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Jan 9, 2020
@mmalerba mmalerba merged commit 31a50f7 into angular:master Jan 9, 2020
yifange pushed a commit to yifange/components that referenced this pull request Jan 30, 2020
Adds tsickle as explicit dependency. This is necessary
because we access it from `node_modules/tsickle` in a
Bazel target that wraps tsc with tsickle.

In the past we just relied on the transitive dependency
of `@angular/bazel` being hoisted, but the hoisting is
not guaranteed if the lock file changes (e.g. when running `yarn
upgrade`). In general, dependencies we explicitly access, should be
added as explicit dependencies.
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Feb 9, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants