Skip to content

feat: Add option to disable ngcc #1620

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

Merged
merged 1 commit into from
Mar 29, 2022
Merged

Conversation

atscott
Copy link
Collaborator

@atscott atscott commented Mar 29, 2022

Running ngcc is required for gathering metadata information of libraries
not published with Ivy instructions. However, ngcc can also be run
manually outside of the extension. Developers may often be running a dev
server which does this step so doing it in the extension as well is
redundant. In addition, there have been issues with running it in VSCode
(#1353, #1444, and potentially other Nx related issues).

This option gives developers the ability to manually opt out of running
ngcc from the extension if it is proving to be problematic for their
setup.

Fixes #1353

Running ngcc is required for gathering metadata information of libraries
not published with Ivy instructions. However, ngcc can also be run
manually _outside_ of the extension. Developers may often be running a dev
server which does this step so doing it in the extension as well is
redundant. In addition, there have been issues with running it in VSCode
(angular#1353, angular#1444, and potentially other Nx related issues).

This option gives developers the ability to manually opt out of running
ngcc from the extension if it is proving to be problematic for their
setup.

Fixes angular#1353
@atscott atscott added the target: minor This PR is targeted for the next minor release label Mar 29, 2022
@atscott atscott requested a review from alxhub March 29, 2022 16:55
@atscott atscott merged commit fbc9e2b into angular:master Mar 29, 2022
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Apr 29, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge Ready to merge cla: yes target: minor This PR is targeted for the next minor release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ngcc fails with error "Too many open files"
2 participants