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
Modules processed by ngcc aren't working (v15) #50735
Comments
I am afraid that without a reproduction or insight into your build pipeline we won't be able to assist here. Since ngcc is no longer present in Angular 16 and v15 is LTS we won't be able to make any changes to ngcc anymore. |
@JoostK
same component in the bad build (btw bad build is 2/3 lesser and some classes are just missing from it):
Maybe someone who have developed ngcc can take a look, because it is looking like ngcc skipped that module and it was compiled in a wrong way. In our package.json we are running ngcc like this
So it is in postinstall |
That would be me. The code you shared is from the final Webpack bundle. ngcc stores its output in the node_modules directory, where you can find each transformed module. The package.json files have been updated with new main fields to redirect module imports to the ngcc-processed; the bundler is then configured to prefer those main fields over the original ones, thereby using the ngcc files. At least that is the theory. As said, without a reproduction or insight into your build pipeline we won't be able to diagnose this issue. |
@JoostK |
@JoostK My another guess is that maybe Our build process (I cut out not related stuff)
|
That sounds plausable; ngcc has to have completed before subsequent build steps can be started. |
Solved: @JoostK thank you for helping with an issue |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Which @angular/* package(s) are the source of the bug?
Don't known / other
Is this a regression?
No
Description
We are experiencing a very complicated and strange bug.
What is the problem:
Old non-ivy angular modules aren’t working without triggering errors. Angular renders just empty structural directives and doesn't emit any errors.
Problems were spotted with:
Important notes:
It may be angular/compiler, webpack, nx, ngcc related.
I've tried to create a minimal reproduction but it was working on a smaller app with exactly same architecture.
So this issue is looking like a race condition. It seems like scss loaders delayed other loaders but now it isn't doing it causing this issue.
Maybe something
ngcc --create-ivy-entry-points
related.If there are any suggestions or similar issues have been seen it would be great. At least answer on a question: "how and why View Engine angular libraries may stop working silently on Angular 15?" will help a lot
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response
The text was updated successfully, but these errors were encountered: