Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
40
Ignite Angular Trial & Samples error entryComponents[]
posted

Just downloaded the Ignite trial and extracted the samples. Not any sample is working on 2 machines, one installed from scatch with the latest Angular & Node versions.The error is always the same, please find below. Any help would be highly appreciated.

./src/styles.scss - Error: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
SassError: Can't find stylesheet to import.
  ╷
1 │ @use 'igniteui-theming/sass/color/functions' as *;
  │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
  node_modules\igniteui-angular\lib\core\styles\base\_mixins.scss 1:1  @forward
  node_modules\igniteui-angular\lib\core\styles\base\_index.scss 2:1   @use
  node_modules\igniteui-angular\lib\core\styles\themes\_core.scss 6:1  @forward
  igniteui-angular\_index.scss 1:1                                     @use
  src\styles.scss 1:1                                                  root stylesheet

./src/styles.scss?ngGlobalStyle - Error: Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
HookWebpackError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
SassError: Can't find stylesheet to import.
  ╷
1 │ @use 'igniteui-theming/sass/color/functions' as *;
  │ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  ╵
  node_modules\igniteui-angular\lib\core\styles\base\_mixins.scss 1:1  @forward
  node_modules\igniteui-angular\lib\core\styles\base\_index.scss 2:1   @use
  node_modules\igniteui-angular\lib\core\styles\themes\_core.scss 6:1  @forward
  igniteui-angular\_index.scss 1:1                                     @use
  src\styles.scss 1:1                                                  root stylesheet

Error: src/app/app.module.ts:26:3 - error TS2345: Argument of type '{ bootstrap: (typeof AppComponent)[]; declarations: (typeof AppComponent)[]; imports: (typeof CommonModule | typeof BrowserModule)[]; providers: undefined[]; entryComponents: undefined[]; schemas: undefined[]; }' is not assignable to parameter of type 'NgModule'.
  Object literal may only specify known properties, and 'entryComponents' does not exist in type 'NgModule'.

26   entryComponents: [],
     ~~~~~~~~~~~~~~~~~~~


× Failed to compile.

  • 0
    Offline posted

    In the Ignite Angular Trial & Samples, encountering errors related to entryComponents can be frustrating. These errors often arise due to uverse packages prices discrepancies in component declarations and module configurations. To resolve them efficiently, cross-check the entryComponents array in your NgModule with the components used in your application, ensuring all components are properly declared and referenced. This meticulous attention to detail can streamline your development process significantly.

  • 2560
    Offline posted

    Hello,

    Could you please clarify which samples are you trying to run and how did you download and isntall Ignite UI for Angular? If you are referring to the bundle available on the Customer Portal named “Ignite UI for Angular 2023 Vol. 1 Complete Bundle”, I have tested running these samples on my side by using the following commands:

    In the "Infragistics_Angular_v23-1\igniteui-angular-examples-LOB” directory:

    npm install –force

    npm run start:live-editing

    While loading takes some time, on my side I am able to successfully run the samples and no errors are raised. Consequently, I am wondering what are the steps you have followed, if my assumption about the repo you are trying to run is correct.

    Apart from that, can I ask if you have checked out our “Getting started with Ignite UI for Angular” topic and if you have followed the steps from there?

    Also my suggestion is to check out our documentation, where for each component there are live demos, which can be opened and viewed directly in the browser, as well as forked and edited in StackBlitz. This might be a more straightforward way of quickly referring to our components features.

    If you require any further assistance on the matter, we will be glad to assist you.

    Best regards,
    Bozhidara Pachilova