Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

primeng not working with ngcc

See original GitHub issue

🐞 Bug report

Command (mark with an `x`)

ng build --prod

Is this a regression?

Description

I have a project with PrimeNg dependency. When I upgraded to 8.0.0-rc.1 my project compiled properly. But if I enable Ivy flag in tsconfig.json:

“angularCompilerOptions”: { “enableIvy”: true, “allowEmptyCodegenFiles”: true },

I get a lot of error messages about incorrect module usage when I build the project.

🔬 Minimal Reproduction

Create new project with Angular CLI 8.0.0-rc.1
Add Primeng dependency and import its modules into AppModule.

🔥 Exception or Error


ERROR in node_modules/primeng/components/confirmdialog/confirmdialog.d.ts(64,22): error TS-996002: Appears in the NgModule.imports of SharedModule, but could not be resolved to an NgModule class
node_modules/ngx-filter-pipe/src/app/shared/ngx-filter-pipe/ngx-filter.module.d.ts(1,22): error TS-996002: Appears in the NgModule.imports of SharedModule, but could not be resolved to an NgModule class

🌍 Your Environment


Angular CLI: 8.0.0-rc.1
Node: 11.3.0
OS: win32 x64
Angular: 8.0.0-rc.1
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.800.0-rc.1
@angular-devkit/build-angular     0.800.0-rc.1
@angular-devkit/build-optimizer   0.800.0-rc.1
@angular-devkit/build-webpack     0.800.0-rc.1
@angular-devkit/core              8.0.0-rc.1
@angular-devkit/schematics        8.0.0-rc.1
@angular/cdk                      8.0.0-beta.2
@angular/http                     8.0.0-beta.10+1.sha-a28b3e3
@angular/material                 8.0.0-beta.2
@ngtools/webpack                  8.0.0-rc.1
@schematics/angular               8.0.0-rc.1
@schematics/update                0.800.0-rc.1
rxjs                              6.4.0
typescript                        3.4.5
webpack                           4.30.0

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:24 (15 by maintainers)

Top GitHub Comments

5reactions

JoostKcommented, Apr 28, 2019

@sergey-morenets at this moment, I’m afraid you can’t yet. We are still experiencing incompatibilities with ngcc for packages that do not follow APF (Angular Package Format), of which PrimeNG is one example. We are working on resolving those incompatibilities in ngcc though.

4reactions

sergey-morenetscommented, Jul 11, 2019

@speige Any updates on this? PrimeNG team recently released 8.0 but it’s not compatible with Angular 8.2.0-next.1 in Ivy mode.

Top Results From Across the Web

PrimeNG error ConfirmationService has not been processed ...

PrimeNG error ConfirmationService has not been processed correctly by ngcc, or is not compatible with Angular Ivy.

Primeng is failing the angular 9 build update - PrimeFaces forum

This likely means that the library (primeng/table) which declares Table has not been processed correctly by ngcc, or is not compatible with ...

Angular v13 is now Available

Get Angular v13 now by running ng update in your project. ... with the latest version of the APF will no longer require...

Upgrading Angular From v8 to v13 - HackerNoon

Add the primeng to the package.json . This will be the most common error because it will occur for all the various dependencies...

Primeng Version7 Is Not Compatible with Angular 9 Ivy

It seems this error occurs during the Ivy compatibility compiler phase ngcc.Ngcc precompile all the entry points of primeng and complains about missing....