igniteui-cli
Ignite UI Command-Line Interface by Infragistics
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/IgniteUI/igniteui-cli with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/IgniteUI/igniteui-cli'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/igniteui--igniteui-cli)HTML
<a href="/listings/igniteui--igniteui-cli"><img src="/api/listings/igniteui--igniteui-cli/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Install the npm package as a global module:
npm install -g igniteui-cli
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 370 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- ## Ignite UI CLI
- <!-- Badges section here. -->
- 
- [](https://coveralls.io/github/IgniteUI/igniteui-cli)
- [](https://badge.fury.io/js/igniteui-cli)
- [](https://discord.gg/39MjrTRqds)
- Quickly create projects, including [Ignite UI for Angular](https://www.infragistics.com/products/ignite-ui-angular) and [Ignite UI for Web Components](https://www.infragistics.com/products/ignite-ui-web-components), for a variety of frameworks.
- ## Overview
- ### Features:
- - Create project structure
- - Add views with Ignite UI components (e.g. Combo, Grid or Chart)
- - Add scenario based templates with multiple components (e.g. a dashboard)
- - Build and install npm packages
- - Select a theme, support for custom themes coming soon
- - Step by step guide
- ### Supported frameworks
- * Angular
- * React
- * Web Components
- * Blazor
- * jQuery
- ### Prerequisites
- The repository houses multiple packages and orchestrates building and publishing them with [lerna](https://github.com/lerna/lerna) and [npm workspaces](https://docs.npmjs.com/cli/using-npm/workspaces).
- To build the repository locally you only need Node.js (CI uses 24.x and 26.x) and the npm that ships with it. Install the dependencies from the repository root with `npm ci`, which installs exactly what `package-lock.json` records. Use `npm install` only when you are changing dependencies, since it can rewrite the lockfile.
- ### Packages
- This monorepo contains several packages that combine into the `igniteui-cli`:
- | Package | Description | Location |
- |-----|-----|-----|
- | [@igniteui/cli-core](https://www.npmjs.com/package/@igniteui/cli-core) | Contains the core functionality of the cli tool | [packages/core](./packages/core) |
- | [@igniteui/angular-templates](https://www.npmjs.com/package/@igniteui/angular-templates) | Contains the template definitions for Angular components | [packages/igx-templates](./packages/igx-templates) |
- | [@igniteui/angular-schematics](https://www.npmjs.com/package/@igniteui/angular-schematics) | IgniteUI CLI implementation to be used with Angular CLI's schematics engine | [packages/ng-schematics](./packages/ng-schematics) |
- | [igniteui-cli](https://www.npmjs.com/package/igniteui-cli) | Standalone IgniteUI CLI tool for React, Blazor, Angular, jQuery and Web Components | [packages/cli](./packages/cli) |
- | [@igniteui/mcp-server](https://www.npmjs.com/package/@igniteui/mcp-server) | MCP server providing AI assistants with Ignite UI documentation and API reference | [packages/igniteui-mcp/igniteui-doc-mcp](./packages/igniteui-mcp/igniteui-doc-mcp) |
- ## Table of Contents
- * [Installation](#installation)
- * [Usage](#usage)
- * [Step by step](#step-by-step)
- * [List available commands](#list-the-available-commands)
- * [Generating Projects and adding components](#generating-projects-and-adding-components)
- * [Generate Ignite UI for Angular project](#generate-ignite-ui-for-angular-project)
- * [Generate Ignite UI for React project](#generate-ignite-ui-for-react-project)
- * [Adding components](#adding-components)
- * [Build and run](#build-and-run)
- * [Search the docs](#search-the-docs)
- * [Check your setup](#check-your-setup)
- * [Configure AI Tooling](#configure-ai-tooling)
- * [MCP Server](#mcp-server)
- * [Using with AI Assistants](#using-with-ai-assistants)
- * [Testing with MCP Inspector](#testing-with-mcp-inspector)
- * [Schematics](#schematics)
- * [Schematic Definitions](#schematic-definitions)
- * [Contribution](#contribution)
- ## Installation
- Install the npm package as a global module:
- ```bash
- npm install -g igniteui-cli
- ```
- ## Usage
- The main entry point is `igniteui` and is also aliased as `ig`. Both can be used interchangeably to call available commands. Check out our [Wiki documentation](https://github.com/IgniteUI/igniteui-cli/wiki) for more details.
- ### Step by step
- To get a guided experience through the available options, simply run:
- ```bash
- ig
- ```
- 
- Upon creation, project will be automatically loaded in the default browser.
- **NOTE**: If that doesn't happen the port may be already in use. Ports vary for different project types, see the description for the [`ig start`](https://github.com/IgniteUI/igniteui-cli/wiki/Start) command for details on default ports.
- ### List the available commands.
- ```bash
- ig help
- ```
- ### Generating projects and adding components
- Create a new project passing name, framework and style theme.
- ```bash
- ig new <project name> --framework=<framework> --type=<proj-type> --theme=<theme>
- ```
- This will create the project and will install the needed dependencies.
- Parameters besides name are optional. Framework defaults to "angular", project type defaults to the first available in the framework and theme to the first available for the project. For more information visit [ig new](https://github.com/IgniteUI/igniteui-cli/wiki/New) Wiki page.
- #### Generate Ignite UI for Angular project
- To create a new project with Ignite UI for Angular use [ig new](https://github.com/IgniteUI/igniteui-cli/wiki/New#creating-ignite-ui-for-angular-applications) by specifying `angular` as framework, and optionally `igx-ts` as project type and selecting one of the [project templates](https://github.com/IgniteUI/igniteui-cli/wiki/New#arguments):
- ```bash
- ig new "IG Project" --framework=angular --type=igx-ts --template=side-nav
- ```
- The project is created with the Angular CLI (`ng new`, then `ng add igniteui-angular`), so this needs network access and always installs the project's packages: `--skip-install` has no effect for Angular projects.
- #### Generate Ignite UI for React project
- To create a new project with Ignite UI for React use [ig new](https://github.com/IgniteUI/igniteui-cli/wiki/New#creating-ignite-ui-for-react-applications-v400) by specifying `react` as framework and `igr-ts` as project type:
- ```bash
- ig new "IG Project" --framework=react --type=igr-ts
- ```
- #### Generate Ignite UI for Web Components project
- To create a new project with Ignite UI for Web Components use [ig new](https://github.com/IgniteUI/igniteui-cli/wiki/New#creating-ignite-ui-for-web-components-applications) by specifying `webcomponents` as framework:
- ```bash
- ig new "IG Project" --framework=webcomponents
- ```
- #### Adding components
- Once you have created a project, at any point you can add additional component templates using [ig add](https://github.com/IgniteUI/igniteui-cli/wiki/Add). Running the command without parameters will guide you through the available templates:
- ```bash
- ig add
- ```
- Add a new component or template to the project passing component ID and choosing a name.
- ```bash
- ig add <component/template> <component_name>
- ```
- The ID matches either a component ("grid", "combo", "text-editor", etc) or a predefined template. Predefined templates are framework/project specific and can provide predefined views with either multiple components or fulfilling a specific use case like "form-validation", "master-detail" and so on.
- For full list of supported templates in the current project you can simply run [ig list](https://github.com/IgniteUI/igniteui-cli/wiki/List) command:
- ```bash
- ig list
- ```
- ### Build and run
- ```bash
- ig build
- ig start
- ```
- ### Search the docs
- `ig doc` searches the documentation bundled with the CLI and prints the results in the terminal. The framework is detected from the current project; pass `-f` outside a project.
- ```bash
- ig doc "row editing" # ranked results with the name of each doc
- ig doc --read grid-row-editing # print one doc by the name from the results
- ig doc "row editing" -f react --limit 5
- ig doc grid --open # search infragistics.com in the browser instead
- ```
- The bundled docs cover Angular, React, Web Components and Blazor. For jQuery use `--open`.
- ### Check your setup
- `ig doctor` checks the environment (Node.js, npm, git, CLI version), the current project (CLI config, installed Ignite UI packages, trial and licensed packages mixed together, Angular version match), the licensed `@infragistics` feed, and the AI setup written by `ig ai-config`. It changes nothing, prints a fix hint next to each warning or failure, and exits with code 1 when a check fails.
- ```bash
- ig doctor
- ig doctor --offline # skip the checks that need the network
- ig doctor --json # machine-readable results
- ```
- ## Configure AI Tooling
- Ignite UI provides rich [AI assisted development toolchain](https://www.infragistics.com/ai-assisted-app-development). To configure Ignite UI AI tooling — MCP servers and AI coding skills — run:
- ```bash
- ig ai-config
- ```
- You will be prompted with two selections:
- - **AI agents** — which tools to generate skill and instruction files for (Generic and Claude are selected by default)
- - **Coding assistants** — which assistants to configure MCP servers for (general `.mcp.json` is selected by default, compatible with Claude Code, VS Code, and others)
- You can also pass options directly:
- ```bash
- ig ai-config --agents claude copilot generic --assistants vscode cursor
- ```
- This creates or updates the assistant-specific MCP config file (e.g. `.mcp.json`, `.vscode/mcp.json`, `.cursor/mcp.json`) with entries for the [Ignite UI MCP](#mcp-server) and `igniteui-theming` MCP servers (existing servers are preserved), copies AI coding skill files from installed Ignite UI packages, and generates agent-specific instruction files (e.g. `CLAUDE.md`, `AGENTS.md`).
- The `ig new` command also prompts for AI tool configuration as part of project creation.
- ## MCP Server
- The CLI includes a bundled [MCP (Model Context Protocol)](https://modelcontextprotocol.io/) server that provides AI assistants with Ignite UI documentation search, API reference lookup, and scaffolding guidance for Angular, React, Blazor, and Web Components.
- Start the MCP server:
- ```bash
- ig mcp
- ```
- The server runs over stdio and supports the following options:
- ```bash
- ig mcp --remote <url> # Use a remote backend instead of the local SQLite database
- ig mcp --debug # Enable debug logging to mcp-server.log
- ```
- ### Using with AI Assistants
- For VS Code, the `ig ai-config` command handles configuration automatically (see above). For other MCP clients (e.g., Claude Desktop, Cursor), configure them manually:
- ```json
- {
- "mcpServers": {
- "igniteui-cli": {
- "command": "npx",
- "args": ["-y", "@igniteui/mcp-server"]
- },
- "igniteui-theming": {
- "command": "npx",
- "args": ["-y", "igniteui-theming", "igniteui-theming-mcp"]
- }
- }
- }
- ```
- In a project that lists `igniteui-cli` as a dependency, `ig ai-config` writes `"args": ["-y", "igniteui-cli", "mcp"]` instead, which starts the server bundled with the project's CLI. Use that form there too when configuring manually: with pnpm, `npx -y @igniteui/mcp-server` cannot start inside such a project.
- The first start downloads the server into the npx cache, which can take 10 seconds or more, and npx downloads it again after each new release. If your MCP client has a short connection timeout, install the server globally (`npm install -g @igniteui/mcp-server`) and use `"command": "igniteui-mcp"` with no arguments, or pin a version (`"args": ["-y", "@igniteui/mcp-server@<version>"]`). Pinned and global installs don't update on their own, so the bundled documentation stays at that version until you change it.
- The MCP server exposes the following tools to AI assistants:
- | Tool | Description |
- |------|-------------|
- | `list_components` | List available Ignite UI component docs. Filter by framework and optional keyword match against filename, component name, keywords, or summary. |
- | `get_doc` | Return the full markdown content of a specific component doc by name (e.g., `grid-editing`, `accordion`). |
- | `search_docs` | Full-text search across Ignite UI docs for a specific framework. Supports prefix matching (e.g., `grid*`). |
- | `search_api` | Search Ignite UI API entries by keyword, feature name, or partial component name. |
- | `get_api_reference` | Return the full API reference for a specific Ignite UI component or class by exact name. |
- | `get_project_setup_guide` | Returns setup guides for creating a new Ignite UI project. For Angular/React/Web Components: CLI scaffolding instructions. For Blazor: `dotnet new` + NuGet setup guide. |
- ### Testing with MCP Inspector
- To interactively test and debug the MCP server tools:
- ```bash
- npx @modelcontextprotocol/inspector ig mcp
- ```
- ## Schematics
- You can also add `Ignite UI for Angular` components to your projects by using the `igniteui/angular-schematics` package. It included schematic definitions for most of the logic present in the [`igniteui-cli`](/packages/cli). These can be called in any existing Angular project or even when creating one. You can learn more about the schematics package on from its [readme](/package/ng-schematics).
- ## Contribution
- See the [Contribution guide](https://github.com/IgniteUI/igniteui-cli/blob/master/.github/CONTRIBUTING.md) to get started.
- ### Run locally
- 1. Clone the repository
- 2. Install dependencies from the repository root with `npm ci` (installs exactly what `package-lock.json` records, for every workspace package, the MCP server included)
- 3. Build everything from the repository root: `npm run build` (compiles the monorepo packages, then builds the MCP server via `build:mcp`)
- 4. Open in Visual Studio Code
- There is a predefined launch.config file for VS Code in the root folder, so you can use VS Code View/Debug window and choose one of the predefined actions. These include launching the step by step guide, create new project for a particular framework or add components.
- 5. Hit Start Debugging/F5
- #### Template smoke test
- `scripts/smoke-test.sh` drives the locally built CLI end to end: it scaffolds a project, adds
- every component template into it, installs, runs `ig doctor`, and builds. The Jasmine specs under `spec/` stub out
- `PackageManager.installPackages`, so they verify that files land on disk but never that the result
- installs or compiles — this script covers that gap.
- ```bash
- npm run build # required: the script runs your local build, not the published CLI
- scripts/smoke-test.sh # angular, react and webcomponents (~20-30 min)
- ```
- Options:
- | Option | Meaning |
- |---|---|
- | `-f, --frameworks LIST` | comma separated; default `angular,react,webcomponents` |
- | `-p, --project ID` | project template to scaffold (default: the framework's own default) |
- | `--all-projects` | scaffold and build every project template, skip component adds |
- | `--templates LIST` | only these component template ids — the fast path when iterating |
- | `--isolate` | one project per component template; slow, use to bisect a failure |
- | `--wizard each\|pairs\|all` | create the projects through the interactive `ig new` wizard instead: every answer (`each`), every pair of answers (`pairs`) or every combination (`all`) |
- | `--skip-build` | scaffold and add only |
- | `--keep` | keep the generated projects even when everything passes |
- | `-o, --out DIR` | work directory (default `output/smoke`, which is gitignored) — **wiped on each run**, see below |
- | `-j, --jobs N` | frameworks to run in parallel (default 1) |
- ```bash
- scripts/smoke-test.sh -f angular --templates grid,combo # quick check, ~2 min
- scripts/smoke-test.sh -f angular --all-projects # every Angular project template
- scripts/smoke-test.sh -f webcomponents --isolate # bisect which template broke
- ```
- Per-step logs land in `<out>/logs/`, and `<out>/results.tsv` is a machine-readable
- `framework / step / template / status / seconds` table. The script exits non-zero if any step
- failed and prints a summary of the failures.
- The work directory is deleted and recreated on every run, so the script refuses to touch anything
- it cannot show is its own: the filesystem root, your home directory, the repository or any directory
- containing it, and any non-empty directory that lacks either the `.smoke-test-workdir` sentinel it
- drops or the `results.tsv` of an earlier run. Point `--out` elsewhere, or remove the directory
- yourself, if you hit that.
- Two things to know if you modify it:
- * **Call the CLI through `cli`, never `packages/cli/bin/execute.js`.** The wrapper delegates to
- `node_modules/igniteui-cli` whenever one resolves inside the current directory, and every project
- template lists `igniteui-cli` as a devDependency. Angular projects install theirs during `ig new`
- (`ng add` needs the packages), so through the wrapper `ig add` would silently switch to the
- *published* CLI and its bundled templates. `cli` loads this checkout's `packages/cli/lib/cli.js`
- instead. For the other frameworks, scaffolding with `--skip-install` still keeps
- `PackageManager.queuePackage` from spawning installs, so dependencies are written to
- `package.json` and installed once at the end.
- * **Exit codes are not sufficient.** `Util.error` logs and returns without setting one, so
- `ig add does-not-exist x` exits 0. Each step is judged on its exit code *and* an error scan of its
- log *and* an artifact check.
- jQuery and Blazor are opt-in via `-f`. jQuery has no build script and 13 of its templates pull
- `ignite-ui-full` from the Infragistics ProGet feed, which needs credentials; Blazor needs the .NET
- SDK and has no component templates, so only `dotnet build` runs.
- #### MCP Server development
- The MCP server at `packages/igniteui-mcp/igniteui-doc-mcp` has its own build pipeline, separate from the monorepo. It uses ESM (ES2022, Node16 modules) while the rest of the monorepo uses CommonJS. See [DEVELOPMENT.md](./packages/igniteui-mcp/igniteui-doc-mcp/DEVELOPMENT.md) for the full MCP server development guide.
- **Build the MCP server** (from the repo root, after `npm ci`):
- ```bash
- npm run build:mcp # Compiles the MCP server and copies the SQLite DB into its dist/ (also part of npm run build)
- ```
- **Regenerate API reference data** (maintainers only):
- The API reference data the server ships (`docs/*-api/`) is committed, so a normal build needs no submodules. To regenerate it after upstream API changes:
- ```bash
- cd packages/igniteui-mcp/igniteui-doc-mcp
- npm run build:docs:all # build:docs:angular-api, :wc-api, :react-api and :blazor-api in turn
- ```
- **Test the MCP server locally:**
- ```bash
- npm run build # includes build:mcp
- node packages/cli/lib/cli.js mcp # Start via CLI
- # or directly:
- node packages/igniteui-mcp/igniteui-doc-mcp/dist/index.js # Start the server
- ```
- #### Building the CLI packages for publishing
- The CLI does not bundle the MCP server: `igniteui-cli` depends on `@igniteui/mcp-server`, which is published from `packages/igniteui-mcp/igniteui-doc-mcp` alongside the other workspace packages. To build them the way the release workflow does:
- ```bash
- npm ci
- npm run build-pack # production build of every package, MCP server included; also refreshes the ai-config skills from the doc submodules
- ```
- `npm pack` in `packages/cli/` and in `packages/igniteui-mcp/igniteui-doc-mcp/` then produces the two tarballs; the MCP one contains the documentation database and the API reference data.
- ## Data Collection
- The Ignite UI CLI tool uses Google Analytics to anonymously report feature usage statistics and basic crash reports. This data is used to help improve the Ignite UI CLI tools over time. You can opt out of analytics before any data is sent by using
- ```bach
- ig config set disableAnalytics true -g
- ```
- when using the CLI. You can read Infragistics privacy policy at https://www.infragistics.com/legal/privacy.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.