Skip to content
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

fix(@angular/cli): add more packages to packageGroup #16309

Closed

Conversation

@alan-agius4
Copy link
Collaborator

alan-agius4 commented Nov 28, 2019

In a workspace users, might have a direct depedencies on packages which are currently not listed in the packageGroup such as @angular-devkit/schematics.

A use-case for this would be that users might have a schematics library in their workspace or using the @angular-devkit/architect-cli with Bazel which is currently in prototype.

Fixes #16307

In a workspace users, might have a direct depedencies on packages which are currently not listed in the `packageGroup` such as `@angular-devkit/schematics`.

A use-case for this would be that users might have a schematics library in their workspace or using the `@angular-devkit/architect-cli` with Bazel which is currently in prototype.

Fixes #16307
@alan-agius4

This comment has been minimized.

Copy link
Collaborator Author

alan-agius4 commented Nov 28, 2019

Following a convo with @clydin. the listed packages are intentionally left out. As the only reason they would be present is if the user was using them directly. And in that case, updating them would most likely break their code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.