Upgrade to Angular 12 #136
Merged
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.
This PR upgrades our Angular version from Angular 11 to Angular 12. This includes upgrading Angular's core libraries to version 12, as well as upgrading peer dependencies to versions that are compatible to Angular 12 (such as upgrading
shallow-render
to a newer version that supports Angular 12). Angular-CLI automates some of the migration process, and these automated changes are included in their own commit. In addition, some manual changes needed to be made to get everything working.To test:
npm install
At the current time, one issue is that we do get a bunch of deprecation warnings from Sass when running any builds/tests/dev servers. However, these are currently not breaking changes, only deprecation warnings. Do we want to tackle that in this PR or just add it as an issue to be resolved separately from the main upgrade?
Note: A lot of these deprecation warnings are related to #127 and would be resolved by fixing it.
Resolves PER-8853: Upgrade to Angular 12. This PR also resolves #131, but not the other dependabot PRs at this time. Also resolves #137.