Angular - Cleanup: drop legacy ngcc compiler support #23384
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.
Description
Resolves https://github.com/volosoft/volo/issues/20391
This PR removes
ngcc
(Angular compatibility compiler) from the project, as it's no longer required in modern Angular versions.Why this update
ngcc
is deprecated and unnecessary when all dependencies support Ivy (angular.dev compiler options).Dependency check
To ensure compatibility, we scanned for any packages still using the legacy View Engine.
The only package identified was:
@abp/utils
How we identified legacy View Engine packages
Find all
*.metadata.json
files (indicates View Engine usage):find node_modules -name "*.metadata.json"
Find all
__ivy_ngcc__
folders (indicates ngcc-processed packages):find node_modules -type d -name "**ivy_ngcc**"
(Optional) List all packages with
metadata.json
for a quick summary:Further reading
Checklist
How to test it?
yarn copy-to:app
command undernpm > ng-packs
and then test the app template accordingly.