Golemui
golemui/golemui
Build, validate, and debug GolemUI forms in React, Angular, Vue, Lit, or vanilla JS.
Install and integrate Ignite UI Web Components packages into React, Angular, Vue 3, LitElement, or vanilla JS/HTML apps, detecting the framework and applying framework-specific setup (package…
Install Igniteui Wc Integrate With Framework
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-integrate-with-framework -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-integrate-with-framework --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/igniteui-wc-integrate-with-framework .claude/skills/igniteui-wc-integrate-with-framework && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "igniteui-wc-integrate-with-framework" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-integrate-with-framework into .claude/skills/igniteui-wc-integrate-with-framework/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-integrate-with-framework", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-integrate-with-frameworkType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-integrate-with-framework -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-integrate-with-framework --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/igniteui-wc-integrate-with-framework .agents/skills/igniteui-wc-integrate-with-framework && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "igniteui-wc-integrate-with-framework" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-integrate-with-framework into .agents/skills/igniteui-wc-integrate-with-framework/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-integrate-with-framework", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-integrate-with-framework -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-integrate-with-framework --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/igniteui-wc-integrate-with-framework .cursor/skills/igniteui-wc-integrate-with-framework && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "igniteui-wc-integrate-with-framework" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-integrate-with-framework into .cursor/skills/igniteui-wc-integrate-with-framework/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-integrate-with-framework", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/IgniteUI/igniteui-webcomponents.git --path skills/igniteui-wc-integrate-with-framework--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-integrate-with-framework -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-integrate-with-framework --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/igniteui-wc-integrate-with-framework .gemini/skills/igniteui-wc-integrate-with-framework && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "igniteui-wc-integrate-with-framework" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-integrate-with-framework into .gemini/skills/igniteui-wc-integrate-with-framework/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-integrate-with-framework", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-integrate-with-frameworkInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-integrate-with-framework -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/igniteui-wc-integrate-with-framework .github/skills/igniteui-wc-integrate-with-framework && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "igniteui-wc-integrate-with-framework" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-integrate-with-framework into .github/skills/igniteui-wc-integrate-with-framework/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-integrate-with-framework", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-integrate-with-framework -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install IgniteUI/igniteui-webcomponents igniteui-wc-integrate-with-framework --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/IgniteUI/igniteui-webcomponents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/igniteui-wc-integrate-with-framework .opencode/skills/igniteui-wc-integrate-with-framework && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "igniteui-wc-integrate-with-framework" agent skill from https://github.com/IgniteUI/igniteui-webcomponents/tree/master/skills/igniteui-wc-integrate-with-framework into .opencode/skills/igniteui-wc-integrate-with-framework/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "igniteui-wc-integrate-with-framework", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
igniteui-wc-integrate-with-framework- GitHub stars
- 170
- Token cost
- ~1.4k tokens
- SKILL.md length
- 488 words
- Files
- 5 (incl. references)
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- MIT
At a glance
Install and integrate Ignite UI Web Components packages into React, Angular, Vue 3, LitElement, or vanilla JS/HTML apps, detecting the framework and applying framework-specific setup (package…
- Works in 4 steps: Detect React → Detect Angular → Detect Vue 3 → …
- Tasks that involve Web performance
- SKILL.md covers Before You Answer, Example Usage, Related Skills and When to Use, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Igniteui Wc Integrate With Framework is an agent skill from IgniteUI/igniteui-webcomponents. Install and integrate Ignite UI Web Components packages into React, Angular, Vue 3, LitElement, or vanilla JS/HTML apps, detecting the framework and applying framework-specific setup (package choice, component registration, theme imports, schemas/config, events and property binding). WHEN TO USE: the user wants to add Ignite UI Web Components or igniteui-react to a project, set up a new app with them, fix registration/'unknown element' errors, or needs framework-specific wiring for templates, events, or forms…
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/angular.md`, `references/react.md` and `references/vanilla-js.md`).
It sits in Frontend & Design, covering Web performance. It works with Angular, React, Vue.js and JavaScript. The repository describes itself as: Ignite UI for Web Components is a complete library of UI components, giving you the ability to build modern web applications using encapsulation and the concept of reusable… The licence is MIT.
When your agent uses it
- Tasks that involve Web performance
Example prompts
- “unknown element”
- “/igniteui-wc-integrate-with-framework”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit a6f3e2c. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Igniteui Wc Integrate With Framework loads about 1.4k tokens when it runs, and up to ~6.5k if it reads all its reference files. Until then it costs about 232 tokens; SKILL.md has 488 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from IgniteUI/igniteui-webcomponents at commit a6f3e2c, republished under its MIT licence (© IgniteUI). 488 words, ~1,380 tokens.
Download SKILL.mdSave it as
.claude/skills/igniteui-wc-integrate-with-framework/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- igniteui-wc-integrate-with-framework
- description
- Install and integrate Ignite UI Web Components packages into React, Angular, Vue 3, LitElement, or vanilla JS/HTML apps, detecting the framework and applying framework-specific setup (package choice, component registration, theme imports, schemas/config, events and property binding). WHEN TO USE: the user wants to add Ignite UI Web Components or igniteui-react to a project, set up a new app with them, fix registration/'unknown element' errors, or needs framework-specific wiring for templates, events, or forms. WHEN NOT TO USE: picking which components to use (use choose-components), customizing themes or styles (use customize-component-theme), trimming bundle size or import granularity (use optimize-bundle-size), building a view from a design (use generate-from-image-design or figma-to-app), or projects using Ignite UI for Angular/Blazor native packages instead of Web Components.
- license
- MIT
- user-invocable
- true
Integrate with Framework
This skill helps users integrate Ignite UI Web Components into their application. It detects the framework or platform in use and loads the appropriate step-by-step integration reference.
Before You Answer
- Choose the package first, then load the framework reference.
- Do not assume every setup flow uses
igniteui-webcomponents. - If the required package is not present in
package.json, add or install the correct Ignite UI dependency first. Absence frompackage.jsondoes not mean the package is invalid.
Package Routing
| Component family | Package |
|---|---|
| General UI components | igniteui-webcomponents |
| Advanced grids | igniteui-webcomponents-grids (trial) @infragistics/igniteui-webcomponents-grids (licensed) |
| Grid Lite | igniteui-grid-lite |
| Dock Manager | igniteui-dockmanager (trial) @infragistics/igniteui-dockmanager (licensed) |
| Charts | igniteui-webcomponents-charts (trial) @infragistics/igniteui-webcomponents-charts (licensed) |
If the request only says "grid", infer the package from the requested features:
- Use
igniteui-webcomponents-gridsfor editing, paging, sorting, filtering, summaries, grouping, hierarchical data, or pivot features. - Use
igniteui-grid-litefor lightweight tabular data.
Example Usage
- "How do I use igniteui-webcomponents in my React app?"
- "Integrate the button component in Angular"
- "Set up igniteui-webcomponents in Vue 3"
- "Help me add web components to my vanilla JS project"
Related Skills
- igniteui-wc-optimize-bundle-size - Reduce bundle size after integration
- igniteui-wc-customize-component-theme - Style components after setup
When to Use
- User wants to add igniteui-webcomponents to a framework project
- User is experiencing framework-specific integration issues
- User needs help with component imports and registration
- User asks about React, Angular, Vue, or vanilla JS setup
Framework Detection
Before loading a reference, identify the target framework from the project context. Check the following signals in order:
1. Detect React
Evidence to look for:
package.jsoncontains"react"or"react-dom"independenciesordevDependencies- Files with
.tsxor.jsxextensions exist insrc/ - Entry point imports
ReactDOMorcreateRoot vite.config.tsuses@vitejs/plugin-reactor@vitejs/plugin-react-swc
→ Load: react.md
Show full SKILL.md (208 more words)Show less
2. Detect Angular
Evidence to look for:
package.jsoncontains"@angular/core"independenciesangular.jsonfile exists in the workspace root- Files with
.component.ts,.module.ts, or.component.htmlpatterns exist - Entry point calls
bootstrapApplicationorplatformBrowserDynamic
→ Load: angular.md
3. Detect Vue 3
Evidence to look for:
package.jsoncontains"vue"independenciesordevDependencies- Files with
.vueextensions exist insrc/ vite.config.tsuses@vitejs/plugin-vue- Entry point calls
createApp
→ Load: vue.md
4. Vanilla JavaScript / HTML (fallback)
Evidence to look for:
- No major framework found in
package.json - Plain
.htmlfiles reference a<script type="module"> - Entry point is a plain
.jsor.tsfile with no framework imports package.jsoncontains "lit" — start with the vanilla JS reference; if using Shadow DOM, follow the Shadow root theming note for grids- User explicitly asks for vanilla JS, HTML, or LitElement integration
→ Load: vanilla-js.md
If the Framework Cannot Be Determined
Ask the user directly:
"What framework or platform are you using? (React, Angular, Vue 3, Vanilla JS / HTML, or LitElement)"
Then load the matching reference from the options above.
Framework Reference Files
| Framework / Platform | Reference |
|---|---|
| React | react.md |
| Angular | angular.md |
| Vue 3 | vue.md |
| Vanilla JS / HTML / LitElement | vanilla-js.md |
Each reference covers:
- Installation
- Theme import (required for styling)
- Component registration
- Usage examples
- TypeScript support
- Platform-specific considerations
- Common issues and solutions
© IgniteUI, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (references) in skills/igniteui-wc-integrate-with-framework of IgniteUI/igniteui-webcomponents.
- SKILL.md
- references/angular.md
- references/react.md
- references/vanilla-js.md
- references/vue.md
Open the folder on GitHubat commit a6f3e2c
Compare with similar skills
Igniteui Wc Integrate With Framework next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Igniteui Wc Integrate With Framework this skillIgniteUI/igniteui-webcomponents | 170 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Golemuigolemui/golemui | 113 | — | ~2.2k | Automated safety check: Pass | MIT | |
| Migrate Webapi Selectallmicrosoft/power-platform-skills | 972 | — | ~5.3k | Automated safety check: Notes | MIT | |
| Creating Docs Code Exampleshandsontable/handsontable | 22k | — | ~2.2k | Automated safety check: Pass | Custom licence | |
| Modern Web GuidanceJetBrains/skills | 364 | 3 repos | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| GSAP Core Animationgreensock/gsap-skills | 16k | 4 repos | ~3.7k | Automated safety check: Pass | MIT |
Similar skills
- Official
Migrate Webapi Selectall
microsoft/power-platform-skills
Reviews and migrates deprecated wildcard () values in Power Pages Web API fields site settings to least-privilege explicit Dataverse columns.
Creating Docs Code Examples
handsontable/handsontable
Sets the rules for writing Handsontable documentation examples in JavaScript, TypeScript, React, Angular and Vue, with the imports, registration and licence key each needs.
- Official
Modern Web Guidance
JetBrains/skills
Search tool for modern web development best practices. An agent skill from JetBrains/skills.
GSAP Core Animation
greensock/gsap-skills
Covers the GSAP core API for tweens, easing, staggers, defaults and matchMedia, and when to choose GSAP over CSS animations or other JavaScript animation libraries.
Boneyard
0xGF/boneyard
Use boneyard-js to add, configure, debug, or rebuild skeleton screens.
More from IgniteUI/igniteui-webcomponents
All 13 skills in this repoIgniteui Wc Customize Component Theme
IgniteUI/igniteui-webcomponents
Theme and style Ignite UI Web Components (and igniteui-react) apps using CSS custom properties, optional Sass, and the igniteui-theming MCP server.
Igniteui Wc Generate From Image Design
IgniteUI/igniteui-webcomponents
Implement application views from design images (screenshots, mockups, wireframes) using Ignite UI Web Components, with the igniteui-cli and igniteui-theming MCP servers for component discovery…
Add Component Property
IgniteUI/igniteui-webcomponents
Add a reactive property to an existing Lit web component with proper decorators, types, tests, specification updates, and documentation
Create New Component
IgniteUI/igniteui-webcomponents
Create a new Lit web component following project conventions, including specification, component class, styles, tests, Storybook story, and exports
Igniteui Wc Choose Components
IgniteUI/igniteui-webcomponents
Identify the right Ignite UI Web Components (igniteui-webcomponents, grids, charts, dock manager, React wrappers) for a UI requirement and point to official docs, examples, and API references.
Igniteui Wc Figma To App
IgniteUI/igniteui-webcomponents
Builds Ignite UI Web Components views from Figma designs, supporting Indigo.Design kits, third-party kits (Material 3, Fluent 2, shadcn/ui, Untitled UI, in-house), and plain frames.
Related
Categories
Questions about Igniteui Wc Integrate With Framework
What does Igniteui Wc Integrate With Framework do?
Install and integrate Ignite UI Web Components packages into React, Angular, Vue 3, LitElement, or vanilla JS/HTML apps, detecting the framework and applying framework-specific setup (package…. Igniteui Wc Integrate With Framework is an agent skill from IgniteUI/igniteui-webcomponents. Install and integrate Ignite UI Web Components packages into React, Angular, Vue 3, LitElement, or vanilla JS/HTML apps, detecting the framework and applying framework-specific setup (package choice, component registration, theme imports, schemas/config, events and property binding).
When should I use Igniteui Wc Integrate With Framework?
Igniteui Wc Integrate With Framework fits situations like: tasks that involve Web performance.
How do I install Igniteui Wc Integrate With Framework in Claude Code?
Run `npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-integrate-with-framework -a claude-code`. Or copy the skill folder (skills/igniteui-wc-integrate-with-framework in IgniteUI/igniteui-webcomponents) into .claude/skills/igniteui-wc-integrate-with-framework in your project. Claude Code loads it when a task matches its description.
How do I install Igniteui Wc Integrate With Framework in Codex?
Run `npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-integrate-with-framework -a codex`. Or copy the skill folder (skills/igniteui-wc-integrate-with-framework in IgniteUI/igniteui-webcomponents) into .agents/skills/igniteui-wc-integrate-with-framework in your project. Codex loads it when a task matches its description.
Can I use Igniteui Wc Integrate With Framework in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add IgniteUI/igniteui-webcomponents --skill igniteui-wc-integrate-with-framework -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/igniteui-wc-integrate-with-framework, .gemini/skills/igniteui-wc-integrate-with-framework, .github/skills/igniteui-wc-integrate-with-framework and .opencode/skills/igniteui-wc-integrate-with-framework in your project.
What does Igniteui Wc Integrate With Framework need to run?
SKILL.md names no scripts, command-line tools or credentials: Igniteui Wc Integrate With Framework is instructions for the agent only.
Does Igniteui Wc Integrate With Framework access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Igniteui Wc Integrate With Framework safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Igniteui Wc Integrate With Framework use?
Igniteui Wc Integrate With Framework is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Igniteui Wc Integrate With Framework use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.1k tokens, read only when the agent opens those files.
What are the alternatives to Igniteui Wc Integrate With Framework?
Skills that share tags, products or a category with Igniteui Wc Integrate With Framework: Golemui (golemui/golemui, 113 stars), Migrate Webapi Selectall (microsoft/power-platform-skills, 972 stars), Creating Docs Code Examples (handsontable/handsontable, 22k stars) and Modern Web Guidance (JetBrains/skills, 364 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Igniteui Wc Integrate With Framework?
IgniteUI (a GitHub organization) maintains it in IgniteUI/igniteui-webcomponents, which has 170 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 7, 2026.
Source: IgniteUI/igniteui-webcomponents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.