Closed ricardosaracino closed 1 year ago
Hey, @ricardosaracino.
We will update migrations to include the following code with the next patch and you will not get that error. Meanwhile you can update angular.json
:
"build": { "options": { "stylePreprocessorOptions": { "includePaths": ["node_modules"] } } }
https://github.com/IgniteUI/igniteui-angular/issues/12439#issuecomment-1342910179
That did fix the issue!!!
I never noticed but you might want to add that the igniteui-theming
package is needed as well.
@Lipata It seems like just changing to node_modules is a bad idea. Wouldn't we end up getting things we don't expect from other packages, and isn't that a ton more work during compilation to look through everything?
Also, if somebody is using the newer versions of yarn, that don't have a node_modules, then what?
perhaps a more explict path node_modules/igniteui-theming
(i did not test this)
@ricardosaracino That didn't work for me, using node_modules/igniteui_theming
Description
I just updated
@infragistics/igniteui-angular
from 14 to 15@use "igniteui-angular/theming" as *;
is causing
I have included this
igniteui-theming
package that i noticed in an example. But even when I go to the_core.scss
my IDE wont resolve it on the@infragistics
project but it does on theigniteui-angular
.What am i missing??!??!?
Packages
this is not resolving