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

Material 2 doesn't seem to be compatible with Angular 2 RC 6 #1156

Closed
naveedahmed1 opened this issue Sep 1, 2016 · 6 comments
Closed

Material 2 doesn't seem to be compatible with Angular 2 RC 6 #1156

naveedahmed1 opened this issue Sep 1, 2016 · 6 comments

Comments

@naveedahmed1
Copy link

naveedahmed1 commented Sep 1, 2016

I recently tried upgrading my project to Angular 2 RC 6 but it seems that Material 2 isn't compatible with RC 6.

When I try to compile my project with RC 6, I receive the below error:

Error Build:Module '"node_modules/@angular/core/index"' has no exported member 'ComponentResolver'. node_modules\@angular2-material\core\portal\portal-directives.d.ts

As per the change log (https://github.com/angular/angular/blob/master/CHANGELOG.md)
ComponentResolver has been depreciated. But since the portal directives uses ComponentResolver , the compiler throws the error.

As per the link angular/angular@73a9ee4 we need to use ComponentFactoryResolver

@m0t0r
Copy link

m0t0r commented Sep 1, 2016

@naveedahmed1 see #1153

@naveedahmed1
Copy link
Author

@m0t0r I upgraded to 2.0.0-alpha.7-12 but now I am receiving below error:

node_modules/@angular2-material/checkbox/checkbox.d.ts(48,14): error TS1005: '=' expected.

@m0t0r
Copy link

m0t0r commented Sep 2, 2016

@naveedahmed1 I think you need to wait for alpha.8. portal-directives.ts on master doesn't use deprecated ComponentResolver. There is #1154 for the upcoming release.

@naveedahmed1
Copy link
Author

I was actually able to compile and run the project after I upgraded Material 2.0.0-alpha.7-12 and upgraded TypeScript to version 2.0.2 Beta

@kara
Copy link
Contributor

kara commented Sep 2, 2016

Using the latest release should resolve this issue, so closing :)

@kara kara closed this as completed Sep 2, 2016
@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 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants