Allow newer major Angular versions#12
Open
DanielKucal wants to merge 1 commit intoSamVerschueren:masterfrom
Open
Allow newer major Angular versions#12DanielKucal wants to merge 1 commit intoSamVerschueren:masterfrom
DanielKucal wants to merge 1 commit intoSamVerschueren:masterfrom
Conversation
Now, when trying to `ng update` to versions > 8, developers will get the following console error: > Package "angular-ga" has an incompatible peer dependency to "@angular/core" (requires "^8.0.0" (extended), would install "12.1.1"). > ✖ Migration failed: Incompatible peer dependencies found. This PR resolves this. Please create a new npm release as well.
Author
|
Just realized I've already created exactly the same few months ago 😅 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Now, when trying to
ng updateto versions > 8, developers will get the following console error:This PR resolves this. Please create a new npm release as well.