Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
@angular/forms 0.1.0 or 0.2.0?
See original GitHub issueBug, feature request, or proposal:
npm complains of unmet peer dependency if @angular/forms 0.2.0 is installed This doesn’t affect build but someone has difficulties with heroku see here
https://groups.google.com/forum/#!topic/angular-material2/CqKY2tcNZqQ
What is the expected behavior?
I’ve patched package.json in slide-toggle, radio, input and checkbox with
"@angular/forms": "^0.2.0"
And npm stops complaining
What is the current behavior?
I think these npm messages confuse because its not clear if they are important
Perhaps a clarification of whether forms 0.2.0 is ok?
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@shotleybuilder When alpha.6 came out, angular core was still on RC.3, with forms 0.1.0. In master, we’ve updated to RC.4 and forms 0.2.0, so as soon as alpha.7 comes out, these peer dependency errors will go away.
When it’s ready 😃