release: some components have a dependency to angular2 beta 8.
See original GitHub issueIt seems like, a few scope components still have a dependency to an older version of angular. (Without scoping packages etc.)
Update: Seems like it’s only card
and checkbox
Issue Analytics
- State:
- Created 7 years ago
- Reactions:3
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Creating A "Run Block" In AngularJS 2 Beta 8 - Ben Nadel
Ben Nadel demonstrates how to create the equivalent of an AngularJS 1.x "run block" in Angular 2 Beta 8.
Read more >Angular versioning and releases
We update peer dependencies in minor versions by expanding the supported versions, but we do not require projects to update these dependencies. Patch...
Read more >Angular2: Testing component with dependency injection
Update: So I kinda ignored component dependency for now and I was able to actually get the component for testing : describe('Login form',...
Read more >"Unable to resolve dependency tree" error during NPM install ...
I am receiving this error message, not entirely sure what it means but I think it might indicate a mismatched version somewhere? I...
Read more >How to Build Your First App with Angular2, JSPM and ASP.NET
This tutorial will show you step-by-step how to build and launch an app with Angular2, JSPM and ASP.NET.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The next milestone should always have a date associated with it. https://github.com/angular/material2/milestones
Should be fixed in the alpha.5 that was released today. (we’ll be setting a target date for alpha.6 in a couple of days)