Repository navigation
29.1.1
Sass
Deep Sass imports resolve through exports in Node and Vite.
The package exports map used an invalid subpath pattern (./sass/**/*.*), so plain deep imports such as @use 'igniteui-theming/sass/themes/schemas' failed in Vite with a "not exported" error. Node's own resolver (require.resolve, import.meta.resolve) rejected these paths too. The pattern is now ./sass/*, and these imports work. If you added aliases or relative-path workarounds for this, you can remove them. pkg: imports through Sass's NodePackageImporter already worked and are unaffected. (#626)
Cleaner CSS from sizable() and pad().
When you pass plain numbers, these functions now put the value directly into the generated expression (e.g. var(--is-small, 1) * 2.5rem) instead of wrapping each one in max(2.5rem, -1 * 2.5rem). Values from var() and calc() behave as before. Rendering doesn't change, but the CSS is smaller and easier to read in DevTools. (#629)
Corrected parameter names in the theme docs.
The docs for three themes listed parameters under the wrong names. If you copied one of these from the docs, compilation failed with No parameter named …:
- chip:
$selected-outlined-background(not$outlined-selected-background) - grid:
$body-column-border-color-odd/$body-column-border-color-even(not$body-column-border-color) - input:
$input-suffix-background--filled(not$input-suffix-background-filled)
The docs also note that chips with a variant (primary, info, success, warning, danger) override $background, $text-color and $border-color. (#623)
MCP server
Generated themes compile for Web Components, React and Blazor.
Before this release, Sass from create_theme and create_component_theme could fail to compile outside Angular:
create_themereferenced palette metadata that it never imported. It now writes the design system out directly.create_component_themedidn't import the theme schemas on non-Angular platforms.- Typography output wrapped Sass variables in quotes, so a literal
'$typeface'ended up in your CSS. It also quoted custom font stacks that were already quoted.
Every style-generating tool now has a test that compiles its output, Angular included. (#628)
Clearer errors for invalid colors.
create_palette and create_theme now check color inputs. Palette failures are reported as errors, so your AI assistant sees that the call failed instead of getting broken output. (#628)
Correct CSS variable names for shadow tokens.
Some themes take a *-shadow parameter but emit the CSS variable as *-elevation, for example resting-shadow becomes --ig-button-resting-elevation. Token lookups now return the real variable name, so overrides suggested by the assistant actually apply. This covers badge, bottom nav, button group, contained and FAB buttons, card, carousel, chip, color picker, dialog and others. (#623)
Color Picker, QR Code and Breadcrumbs support.
The MCP server now knows these components, so it can look up their tokens and generate themes for them. (#622)