-
Notifications
You must be signed in to change notification settings - Fork 6.8k
angular4 support #3900
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
Comments
I believe @Mscu is this hasn't been released yet so he is not getting the update. |
The others pretty much covered it: the next release will include Angular 4 support. |
Hi @crisbeto, could you please give us more information about when the next version will be released? |
It should be within a few days @basst314. If you don't want to wait for it, you can install the build from
|
Specified @angular/blah 4.0.0 in package.json but getting unmet peer on @angular 4.0.1. running the above command. Does it really "depend" on that patch? |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
please provide a release that is working with the angular 4 final version. The latest release currently still relies on angular 2.x and even in the master its just the rc.
What is the expected behavior?
What is the use-case or motivation for changing an existing behavior?
updating angular to version 4.0
Which versions of Angular, Material, OS, browsers are affected?
angular 4
The text was updated successfully, but these errors were encountered: