3.0.0-rc.11 peer dependency update is a breaking change
See original GitHub issueVersion
3.0.0-rc.11
Node and OS info
all
Steps to reproduce
If your version is set to allow minor updates, for example: “@vue/cli-service”: “^3.0.0-rc.10”, then when you install, you get version 3.0.0-rc.11. The move of vue-template-compiler to the peer dependencies broke the build
npm WARN @vue/cli-service@3.0.0-rc.11 requires a peer of vue-template-compiler@^2.0.0 but none is installed. You must install peer dependencies yourself.
What is expected?
Premajor changes shouldn’t break build
What is actually happening?
Premajor change added a peer dependency that is breaking the build.
This is fixable by adding this to the deps or pegging the version explicitly.
Thanks!
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Angular update from 8 to 13 peer dependency problem
Found it ! That was a problem with my node version. I was using v16.9 and install node v14.19 solve my problem. I...
Read more >Update to Angular 11 Version - Angular Wiki
Package "codelyzer" has an incompatible peer dependency to "@angular/compiler" (requires ">=2.3.1 <10.0.0 || >9.0.0-beta <10.0.0 ...
Read more >angular npm install and npm audit fix is breaking on ... - Reddit
I moved from my development PC to remote server, to make builds on remote. I did npm i but still getting messages say...
Read more >Introducing Yarn 2 ! - DEV Community
Breaking changes... Configuration settings have been normalized; Packages must respect their boundaries; Bundle dependencies aren't ...
Read more >npm audit fix 의경우 - 코딩애플 온라인 강좌
npm WARN ERESOLVE overriding peer dependency ... Will install react-scripts@3.4.4, which is a breaking change ... wrap-ansi 3.0.0 - 6.1.0
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 Free
Top 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
Once we release official 3.0
^
will be fine as we will stick to semver and avoid breaking changes. Also this change was technically not breaking between RCs. It broke because of an upgrade from beta-scaffolded project.Word, thanks man! I was trying to align the code to the latest so we are ready for the stable 3.0 without much effort.
Really appreciate all your work on vue & the cli by the way! We are using it for all our new projects, its just phenomenal all around.