这是indexloc提供的服务,不要输入任何密码
Skip to content

Angular - Cleanup: drop legacy ngcc compiler support #23384

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: rel-9.3
Choose a base branch
from

Conversation

sumeyyeKurtulus
Copy link
Contributor

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

  • Ivy has been the default rendering engine since Angular 12.
  • Angular 17 fully removed support for the legacy View Engine (Angular roadmap).
  • 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

  1. Find all *.metadata.json files (indicates View Engine usage):

    find node_modules -name "*.metadata.json"
  2. Find all __ivy_ngcc__ folders (indicates ngcc-processed packages):

    find node_modules -type d -name "**ivy_ngcc**"
  3. (Optional) List all packages with metadata.json for a quick summary:

    find node_modules -name "*.metadata.json" | sed 's|/node_modules/|/|g' | awk -F/ '{print $2}' | sort | uniq

Further reading

Checklist

  • I fully tested it as developer / designer and created unit / integration tests

How to test it?

  • You need to run yarn copy-to:app command under npm > ng-packs and then test the app template accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants