ERROR in IgxNumberFormatSpecifier cannot be used as an entry component.

[matpinsdorf]

Description

Hi , i updated my aplication to angular 10 and updated igniteui-angular to the latested version, now i cant build it anymore, i got the follwing error: "ERROR in IgxNumberFormatSpecifier cannot be used as an entry component." but i dont know what or where is this "IgxNumberFormatSpecifier ", before the update when i was using angular 9 and a previous version of igniteui-angular everything was right.

• igniteui-angular version:
  10.2.0-beta.1

[gmurray81]

@matpinsdorf are you loading one of our *Dynamic modules?

[matpinsdorf]

@matpinsdorf are you loading one of our *Dynamic modules?
@gmurray81
iam not sure ....
we are using several infragiscs components including" igniteui-angular-charts"

[gmurray81]

If you look in your app module, or other modules in your application, you should see one or more of our modules imported.
I suspect one of those will end in DynamicModule. A few of those may have a regression issue in the current version.

The good news is that those are for very edge case scenarios that may not pertain to your application, and you can probably just import the version that ends in Module instead of DynamicModule, unless you have one of those very specific scenarios.

[matpinsdorf]

hi @gmurray81 thanks for the help, but i looked in all of our modules and we are not using any DynamicModule, the only place i see imports using then is inside igniteui-angular-charts.

[gmurray81]

Hmm.... could you tell me which imports you do have in your App module? In terms of things from our packages?

[matpinsdorf]

Sure !

here is all of our "igniteui-angular" and "igniteui-angular-charts" imports , we are not importing then in App Module, we are importing then in a specific module:

import { IgxMaskModule,
IgxGridModule,
IgxTreeGridModule,
getCurrentResourceStrings,
changei18n }
from 'igniteui-angular';

import {
IgxCategoryChartModule,
IgxPieChartModule,
IgxDoughnutChartModule,
IgxDataChartCoreModule,
IgxDataChartCategoryModule,
IgxLegendModule,
IgxItemLegendModule,
IgxDataChartInteractivityModule,
IgxDataChartStackedModule,
IgxDataChartPolarCoreModule,
IgxDataChartPolarModule,
IgxDataChartRadialCoreModule,
IgxDataChartRadialModule,
IgxDataChartScatterCoreModule,
IgxDataChartScatterModule,
IgxBarSeriesComponent,
IgxStackedBarSeriesComponent,
IgxStackedColumnSeriesComponent,
IgxStackedAreaSeriesComponent,
IgxStacked100AreaSeriesComponent,
IgxStacked100BarSeriesComponent,
IgxStacked100ColumnSeriesComponent,
IgxStackedLineSeriesComponent,
IgxStacked100LineSeriesComponent,
IgxStackedSplineAreaSeriesComponent,
IgxStacked100SplineAreaSeriesComponent,
IgxStackedSplineSeriesComponent,
IgxStacked100SplineSeriesComponent,
IgxRingSeriesComponent,
IgxCategoryXAxisComponent,
IgxCategoryYAxisComponent,
IgxNumericXAxisComponent,
IgxNumericYAxisComponent,
IgxCategoryAngleAxisComponent,
IgxNumericAngleAxisComponent,
IgxNumericRadiusAxisComponent,
IgxCalloutLayerComponent,
IgxPieChartComponent,
IgxAreaSeriesComponent,
IgxColumnSeriesComponent,
IgxLineSeriesComponent,
IgxPointSeriesComponent,
IgxSplineAreaSeriesComponent,
IgxSplineSeriesComponent,
IgxStepAreaSeriesComponent,
IgxStepLineSeriesComponent,
IgxWaterfallSeriesComponent,
IgxPolarScatterSeriesComponent,
IgxPolarLineSeriesComponent,
IgxPolarAreaSeriesComponent,
IgxPolarSplineSeriesComponent,
IgxPolarSplineAreaSeriesComponent,
IgxRadialLineSeriesComponent,
IgxRadialColumnSeriesComponent,
IgxRadialPieSeriesComponent,
IgxRadialAreaSeriesComponent,
IgxRangeAreaSeriesComponent,
IgxRangeColumnSeriesComponent,
IgxScatterSeriesComponent,
IgxScatterLineSeriesComponent,
IgxScatterSplineSeriesComponent,
IgxBubbleSeriesComponent,
} from 'igniteui-angular-charts';

[zdrawku]

@matpinsdorf I want to be sure that the issue still persists. I don't think that the problem is coming from igniteui-angular library, but still could you please verify that you've updated both libraries to their latest available versions.

[gmurray81]

@matpinsdorf I believe I know what the underlying issue is, but I'm not really sure why you would be hitting it for your scenario.

I was actually asking which of our modules you had added to the imports collection of your app's NGModules,

[gmurray81]

ah or are you not using explicit modules?

[matpinsdorf]

@zdrawku everything is updated, but
unfortunately the error persists

[matpinsdorf]

@gmurray81 were are importing this modules:

[gmurray81]

Thanks @matpinsdorf, that should give us enough info to reproduce the issue, and I might be able to get you a work around faster than we can get an update out there.

[gmurray81]

Hmm... I'm still unable to reproduce the issue. @matpinsdorf could you tell me more details about what version of angular and angular compiler you are using? Anything special about the build toolchain?

I can proceed with resolving what I assume to be the issue, but I'm still confused as to why you are running into it at all, as it doesn't seem like you should be hitting it.

[matpinsdorf]

hi @gmurray81 we re are using this versions now :

but the problem started when upgraded from version 9 to 10.

[gmurray81]

This should be fixed in the next package.