What's New in Ignite UI CLI 15.8.1 – resolve_import, Unified Docs & 60+ New Templates

Ignite UI CLI 15.8.1 is out. Here’s what’s new:

• A new resolve_import MCP tool that gives AI assistants exact import paths
• A smarter MCP documentation search and API reference lookup
• A unified documentation pipeline for Angular, React, Web Components and Blazor
• New component templates across Angular, React and Web Components
• Updates to Angular 22.2 and igniteui-webcomponents 7.4.1
• Fixes for ai-config ordering, CLI interruption handling and MCP Registry publishing

Template coverage grows (15.7.0 → 15.8.0)

The latest releases add templates for many more components across Angular, React and Web Components.

15.7.0 additions

• Angular: templates for 29 components, including Action Strip, Avatar, Badge and Banner
• Web Components: templates for 20+ components - such as color picker, QR code, Virtual Scrolling and many more
• React (igr-ts): templates for 20 components, with styles and tests

15.8.0 additions

• React: new igr-ts templates for Breadcrumbs, Color Picker (standard and alpha), QR Code and Virtual Scroll
• Web Components: new Breadcrumb template (IgcBreadcrumb)
• Component groups are reorganized across Angular, React and Web Components for clearer categorization and easier navigation

React scaffolds now use igniteui-react and igniteui-react-grids ~19.9.0, and chart/gauge templates use ~19.6.0.

MCP server: better answers for AI assistants

The MCP server remains the heart of the AI-assisted workflow. These releases focus on making it more accurate.

New: resolve_import

AI assistants often get a component right but the import path wrong. resolve_import returns exact import statements for symbols, grouped by module, across Angular, React, Web Components and Blazor.

Smarter docs and API lookups (15.8.0)

• get_doc now has a fallback search when no exact document matches
• get_api_reference supports case-insensitive lookups and fuzzy component matching

One documentation source (15.8.1)

The bundled documentation is now built from the unified igniteui-documentation repository. It replaces the archived igniteui-docfx and igniteui-xplat-docs sources.

• Angular, React, Web Components and Blazor docs come from one source
• A single MDX exporter replaces four per-framework export scripts. It preserves code fences, Angular environment URLs, stable doc names and unprefixed API symbol names
• The bundled documentation database has been rebuilt from the new source
• The MCP server README now has expanded installation and configuration guidance

More reliable MCP Registry publishing

Publishing to the MCP Registry now runs as a separate job. It waits for the new @igniteui/mcp-server version to appear on npm and retries. This fixes failed registry publishes immediately after an npm release. A manual trigger can also publish an existing release tag.

Framework updates

• Angular: new projects target Angular and Ignite UI for Angular ~22.2.0
• Web Components: projects use igniteui-webcomponents ~7.4.1

Fixes and polish

• ai-config order in ng new: AI configuration now runs before package install, so you don’t get premature prompts
• Ctrl+C during install: interrupting a package install now exits with code 130
• TypeScript expression collector: now compares true/false/null literals and string or numeric property names correctly
• Framework menu: improved visibility, and the None option is now exclusive (15.7.0)
• Schematics: a valid project template is resolved before packages are upgraded (15.7.0)
• Generated projects: MCP configuration files are no longer included (15.7.0)
• Dependency updates, including Hono, Axios, js-yaml, minimatch, lodash and immutable

Update to the latest

npm install -g igniteui-cli@latest
ig --version

Then scaffold a project and set up AI tooling:

ig new my-app
ig ai-config

FAQ

What is resolve_import? An MCP tool that returns the exact import statement for a component or symbol, so AI assistants don’t have to guess the import path.

Which frameworks does it cover? Angular, React, Web Components and Blazor.

Do I need to change anything for the new documentation source? No. The MCP server ships with the rebuilt documentation database.

Which Angular version do new projects use? Angular and Ignite UI for Angular ~22.2.0.

Is there a 15.7.1 release? Not as a GitHub release. 15.7.0 is the previous baseline.

Get started

• Ignite UI CLI release notes on GitHub
• Ignite UI CLI 15 – MCP Server, ai-config & Blazor Scaffolding
• GitHub Discussions for feedback and questions

Try it on a new project and let us know how it goes in GitHub Discussions.