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(ng-add): material version could not be determined #12751

Merged

Conversation

devversion
Copy link
Member

Due to the fact that the CLI only installs @angular/material when running ng add and expects us to add the entries to the package.json, we cannot use the VERSION object from @angular/material because the Material package tries to require the CDK (which is not present at this point). This results in a runtime exception that will cause the materialVersion to be null.

In order to properly determine the Material version that comes with the ng add command, we should gracefully inspect the according package.json file of the @angular/material or @angular/cdk package.

Due to the fact that the CLI **only** installs `@angular/material` when running `ng add` and expects us to add the entries to the `package.json`, we cannot use the `VERSION` object from `@angular/material` because the Material package tries to `require` the CDK (which is not present at this point). This results in a runtime exception that will cause the `materialVersion` to be `null`.

In order to properly determine the Material version that comes with the `ng add` command, we should gracefully inspect the according `package.json` file of the `@angular/material` or `@angular/cdk` package.
@devversion devversion added P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful pr: merge safe target: major This PR is targeted for the next major release labels Aug 20, 2018
@devversion devversion requested a review from amcdnl as a code owner August 20, 2018 11:39
@googlebot googlebot added the cla: yes PR author has agreed to Google's Contributor License Agreement label Aug 20, 2018
Copy link
Member

@jelbourn jelbourn left a comment

Choose a reason for hiding this comment

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

LGTM

@jelbourn jelbourn added pr: lgtm action: merge The PR is ready for merge by the caretaker labels Aug 20, 2018
@jelbourn jelbourn merged commit a027ae5 into angular:master Aug 20, 2018
@devversion devversion deleted the fix/ng-add-material-version-not-determined branch August 20, 2018 20:38
@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 Sep 9, 2019
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 P1 Impacts a large percentage of users; if a workaround exists it is partial or overly painful target: major This PR is targeted for the next major release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants