# syncfusion-react-license

Walks through Syncfusion licensing in React apps: issuing a key, registering it, and clearing validation errors. Useful when your build starts warning about licenses.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 718 installs · ★ 3
- Author: Syncfusion Inc
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/syncfusion/react-ui-components-skills/tree/HEAD/skills/syncfusion-react-license/SKILL.md
- Updated: 2026-10-23
- HTML: https://affpapa.org/en/nevibecode/skills/syncfusion-react-license

## What it does

This skill covers Syncfusion license keys for React: how to generate one, how to register it, and why a validation warning shows up. It ships reference files for key generation, registration, and the common error cases.

The part that trips people up: a key is tied to a version and to either a platform or an edition. From 31.1.17 the split is by edition — UI Edition, Document SDK, PDF Viewer SDK, DOCX Editor SDK, Spreadsheet Editor SDK, Enterprise Edition. In 30.x.x and earlier keys were issued per platform such as React, JavaScript or Angular. The unlock key from the installer is a different thing and will not validate in code.

The suggested route is the `SYNCFUSION_LICENSE` environment variable, then `npx syncfusion-license activate`, then clearing `node_modules/.cache`. Validation runs offline, so the running app needs no network. A key that does not match the installed package version or platform throws an error — regenerate it for the right version.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add syncfusion/react-ui-components-skills --skill syncfusion-react-license -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/syncfusion-react-license/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/syncfusion-react-license/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add syncfusion/react-ui-components-skills --skill syncfusion-react-license -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/syncfusion-react-license/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add syncfusion/react-ui-components-skills --skill syncfusion-react-license -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/syncfusion-react-license/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install syncfusion/react-ui-components-skills syncfusion-react-license
```

2. **Manually: put the files in place**
- File: `.github/skills/syncfusion-react-license/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add syncfusion/react-ui-components-skills --skill syncfusion-react-license -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/syncfusion/react-ui-components-skills --path skills/syncfusion-react-license
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/syncfusion-react-license/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add syncfusion/react-ui-components-skills --skill syncfusion-react-license -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/syncfusion/react-ui-components-skills/tree/HEAD/skills/syncfusion-react-license/SKILL.md

## When to use it
- generate a license key for the Syncfusion version you actually use
- register the key through an environment variable instead of committing it
- work out why a license validation warning appears
- tell a license key apart from the installer unlock key
- wire key registration into a CI/CD pipeline

## Example prompts
- Why is my build warning about the Syncfusion license?
- How do I register `SYNCFUSION_LICENSE` in a React app?
- I'm getting a version mismatch error on my Syncfusion key

## Similar
- [oss-license-strategy](https://affpapa.org/en/nevibecode/skills/oss-license-strategy.md) — skill · 10500 installs
- [vercel-react-view-transitions](https://affpapa.org/en/nevibecode/skills/vercel-react-view-transitions.md) — skill · 168100 installs
- [react](https://affpapa.org/en/nevibecode/skills/react.md) — skill · 16300 installs
- [clerk-react-router-patterns](https://affpapa.org/en/nevibecode/skills/clerk-react-router-patterns.md) — skill · 15500 installs
- [react-email](https://affpapa.org/en/nevibecode/skills/react-email.md) — skill · 12600 installs
- [react-expert](https://affpapa.org/en/nevibecode/skills/react-expert.md) — skill · 5500 installs

From the same set: [syncfusion/react-ui-components-skills](https://affpapa.org/en/nevibecode/by/syncfusion/react-ui-components-skills.md) — 57 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md