[adrianptrv]

Follow-up to this theming PR: IgniteUI/igniteui-theming#668

Description

What changed

• The theme generator (core/src/core/styles/themes/generators/_base.scss) declares --ig-theme and --ig-theme-variant with igniteui-theming's new theme-markers() mixin instead of writing them by hand. The output is the same.

Output changes from the igniteui-theming update

• css-vars-from-theme() no longer emits the markers, so the scrollbar() mixin, which calls it directly, no longer declares them on its parent and on .ig-scrollbar.
• component-tokens() goes through tokens($mode: 'scoped'), which still declares the markers, so component output is unchanged.

Type of Change (check all that apply):

• Refactoring (no functional changes)

How Has This Been Tested?

• Manual testing

Checklist:

• All relevant labels have been applied to this PR

Waiting on

• igniteui-theming version that includes the theme-markers() mixin.

[Copilot]

🟢 Approval recommended

No active review issues are reported for the theme-marker mixin and dependency updates.

No open issues 🎉

What changed in this PR

Updates Angular’s theme generator to use igniteui-theming’s theme-markers() mixin, following the upstream theming refactor while preserving the generator’s marker output.

Changes:

• Replaces handwritten --ig-theme and --ig-theme-variant declarations with theme-markers().
• Updates library and workspace dependencies to igniteui-theming ^30.2.0 and locks version 30.2.0.

File	Description
projects/​igniteui-angular/​package.json	Updates the library’s theming dependency range.
projects/​igniteui-angular/​core/​src/​core/​styles/​themes/​generators/​_base.scss	Uses the shared mixin to emit theme markers.
package.json	Updates the workspace’s theming dependency range.
package-lock.json	Locks the updated theming package and integrity hash.

_{Review effort: Balanced}