Skip to content
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

Unable to debug error "ngcc failed to run..." #1364

Closed
Jinnie opened this issue Jan 15, 2021 · 3 comments
Closed

Unable to debug error "ngcc failed to run..." #1364

Jinnie opened this issue Jan 15, 2021 · 3 comments

Comments

@Jinnie
Copy link

Jinnie commented Jan 15, 2021

Description:
We have troubles compiling projects which include the Clarity library (https://github.com/vmware/clarity) on Stackblitz with Ivy enabled.

Steps to reproduce:

  • Deploy clean Angular project.

  • Add these dependencies to package.json:

    "@clr/angular": "^4.0.0",
    "@clr/icons": "^4.0.0",
    "@clr/ui": "^4.0.0",
    "@webcomponents/custom-elements": "^1.0.0",

Live reproduction:
https://stackblitz.com/edit/angular-ivy-issue-repro?file=package.json

Result:
ngcc failed to run on @clr/angular@4.0.9

Expectations:
We are unable to debug the issue based on this error message only. We would appreciate any additional information or logs.

Notes:

  • Downloading and building the project locally works.
  • It works fine with Ivy off.
@waterplea
Copy link

Same happens with Taiga UI:
taiga-family/taiga-ui#109

Here's our starter that fails if you enable Ivy (although library itself works fine with Ivy):
https://stackblitz.com/edit/taiga

@BenRacicot
Copy link

BenRacicot commented Dec 14, 2021

Seeing this on a basic Angular 13 setup with NGXS, FullCalendar, etc.

ngcc failed to run on @ngxs/store@3.7.3.

Shouldnt Angular 9+ Stackblitzes have no "Enable Ivy" option and be using Ivy by default? This may simplify the ngcc process (just an idea)

@github-actions
Copy link

Apologies that we were unable to address this issue in a timely manner!

Given that we have millions of free users this has been a challenge, and we are working to improve over time. As part of an effort to focus on driving the most recent issues to resolution, this issue is being closed.

If this issue is still meaningful, please comment with an update and re-open the issue for troubleshooting! Thanks for your continued loyalty to the StackBlitz platform over the years!

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

No branches or pull requests

4 participants