Compatibility
Simurgh is pre-release. Compatibility runs in CI: every pull request runs the oldest and newest supported framework peers against Chromium, Firefox, and WebKit. CI also runs every seven days to detect browser changes. A peer range allows installation; this matrix provides evidence at both supported edges.
Framework compatibility
Section titled “Framework compatibility”| Adapter | Declared peer requirement | Repository development version | CI verification |
|---|---|---|---|
@simurgh-ui/react | React >=18 and React DOM >=18 | React 19.2.8 | React 18 and 19 on Chromium, Firefox, and WebKit. |
@simurgh-ui/vue | Vue >=3.4 | Vue 3.5.41 | Vue 3.4 and 3.5 on Chromium, Firefox, and WebKit. |
@simurgh-ui/angular | Angular Core and Common >=18 | Angular 20.3.27 | Angular 18 and 20 on Chromium, Firefox, and WebKit. |
The matrix verifies the lower and upper supported edges rather than every minor release. Failures at either edge block a merge.
Install only one framework adapter in a consuming application. Framework peer dependencies remain the application’s responsibility; Simurgh does not bundle React, Vue, or Angular into the adapter.
Runtime and tooling
Section titled “Runtime and tooling”| Tool | Requirement or verified version |
|---|---|
| Package format | ECMAScript modules with TypeScript declarations. The application bundler must resolve package exports. |
| Package manager | Any package manager that installs peer dependencies and package exports; this repository and CLI examples use pnpm. |
| pnpm | Repository builds are pinned to 11.16.0. Consumer applications do not need this exact version unless reproducing the monorepo. |
| Node.js | CI builds, CLI fixtures, and quick starts run on Node.js 22. No broader CLI engine range is declared yet. |
| TypeScript | Component declarations are produced with TypeScript 5.9.2 in the repository. Consumers should use a version compatible with their selected framework. |
The packages do not currently declare a Node engines field. Node 22 is therefore the verified CLI
environment, not a promised minimum. Browser-delivered component code must still be processed by a
framework-compatible application build.
Browser support
Section titled “Browser support”Every pull request runs the documentation browser suite against the current Playwright builds of:
- Chromium, using the Desktop Chrome device profile
- Firefox, using the Desktop Firefox device profile
- WebKit, using the Desktop Safari device profile
This provides engine-level coverage for current Chromium, Gecko, and WebKit behavior. It does not promise support for an arbitrary historical browser version, embedded webview, or assistive technology/browser combination. Simurgh uses modern platform features, including CSS custom properties, logical properties, native form controls, and ECMAScript modules.
Applications with a formal browser policy should run their own production build and task-based component scenarios on the exact browser versions in that policy. Pay particular attention to native Select and date/file controls, focus-visible presentation, portal stacking, mobile virtual keyboards, forced colors, and RTL scrolling.
What CI verifies
Section titled “What CI verifies”The compatibility gate currently includes:
- Frozen dependency installation on Ubuntu and Node.js 22.
- Lint, type checking, framework compilation, unit and accessibility contract tests.
- React, Vue, and Angular package-import quick starts.
- React, Vue, and Angular CLI source-copy quick starts.
- Production documentation build and package-export validation.
- Bundle-size and Angular production compilation fixtures.
- Playwright scenarios in Chromium, Firefox, and WebKit.
CI does not yet cover Windows/macOS builds, mobile-device hardware, all supported framework minor versions, screen-reader automation, or legacy browsers. These are compatibility gaps rather than implicit support claims.
Reporting a compatibility problem
Section titled “Reporting a compatibility problem”Include the Simurgh package and version, installation model, framework and version, TypeScript, Node.js and package manager when relevant, browser/OS, and a minimal reproduction. State whether the problem occurs in development, SSR, hydration, or a production build and whether it reproduces with recipes disabled.
Last verified on 2026-08-13 against Simurgh registry 0.1.1.