After migrating from version 11 to 14 (1 step at a time), I'm having issues with the custom components themes. Components styles do not follow the provided themes anymore.
Used version:
Hello Benoit,
Thank you for reaching out.
I noticed that you are using the licensed version of Ignite UI for Angular:
Benoit Tassin said:"@infragistics/igniteui-angular": "^14.0.2",
and you are trying to import the themes for the free version:
Benoit Tassin said:I tried to switch the @import to `@use "igniteui-angular/theming" as *;`
Can you please try to import the themes using the path for licensed version and let me know if this worked.
// licensed version: @use '@infragistics/igniteui-angular/theming' as *;
Regards,Viktor KombovEntry Level Software DeveloperInfragistics, Inc.
Hello, Is there a solution for this issue?
I'm using licensed version:
Hi Sampat,
Since I see that the Ignite UI for Angular version you are using is 15, I am wondering if you have followed thе manual steps from the “From 14.2.x to 15.0.x” update guide in our documentation?
Mainly, the following “stylePreprocessorOptions” configuration has to be added in the angular.json:
"stylePreprocessorOptions": { "includePaths": ["node_modules"] }
My assumption is that this is what is missing on your side.
Just to clarify, the reason you are not finding the theming module as a directory is that it is rather a path to the module, pointing to the original stylesheet:
"exports": { .. "./theming": { "sass": "./lib/core/styles/themes/_index.scss" }, "./themes": { "sass": "./lib/core/styles/themes/_index.scss" }, … }
The exports object is part of the package.json file, located in @infragistics/igniteui-angular.
Please, try adding the preprocessor configuration in your app and let me know if it resolves the build error. Also, please, keep in mind that we recommend creating separate threads or support cases for individual queries. This is to ensure that all your issues are addressed correctly. Thank you for understanding.
Best regards,
Bozhidara Pachilova