FOUNDATION

Versioning & Compatibility

Know exactly which Angular, runtime and browser environments are covered before installing a release. Compatibility is a tested contract, not an optimistic version label.

Angular 22.xModern browsersSSR and hydration

CURRENT CONTRACT

Angular 22 is the first line

NeuralNg is being prepared for its first public alpha. There is no previously published consumer release and therefore no migration history to preserve yet. The current package manifests declare Angular ^22.0.0; that means Angular 22.x, not every future Angular major.

“Angular 22+” describes direction, not an untested promise

NeuralNg will follow Angular forward, but a new major becomes supported only after peer ranges, compilation, unit tests, package smoke tests, SSR and browser E2E all pass on that major.

{
  "peerDependencies": {
    "@angular/common": "^22.0.0",
    "@angular/core": "^22.0.0",
    "@angular/forms": "^22.0.0",
    "@angular/router": "^22.0.0"
  },
  "peerDependenciesMeta": {
    "@angular/forms": { "optional": true },
    "@angular/router": { "optional": true }
  }
}

Packages have different boundaries

Do not copy the MCP server's Node requirement onto browser-only packages. Each package publishes only the constraints required by its own runtime.

Package	Current contract	Runs in
@neural-ng/core	Angular 22.x; Forms and Router optional	Browser, SSR and prerender
@neural-ng/editor	Angular 22.x and matching Core alpha line	Browser with SSR-safe initial rendering
@neural-ng/icons	Framework-independent CSS package	Any standards-based browser
@neural-ng/theme	Node 24.x for CLI; browser export available	Build tooling or browser compiler
@neural-ng/mcp-server	Node 24.x	Local stdio process

How a new Angular major is admitted

A compatible TypeScript or RxJS version is selected through Angular's own compatibility matrix. Consumers should not override Angular's compiler matrix merely to install NeuralNg.

1
Install the major
Update the workspace and every Angular peer dependency together.
2
Compile public entry points
Core, Editor, themes, icons and secondary entry points must package cleanly.
3
Exercise behavior
Forms, overlays, keyboard flows, SSR and hydration run against the candidate.
4
Publish the claim
Only then does the peer range and this matrix include the new major.

Angular version compatibility Angular release policy

Runtime requirements

Core components run inside your Angular application, so the supported Node and TypeScript versions come from your selected Angular major. Executable NeuralNg tools declare their own Node requirement and must be checked separately before installation.

Angular application

Follow the official Node.js and TypeScript matrix for your application's Angular major.

MCP Server

The @neural-ng/mcp executable currently requires Node.js 24.x.

Theme CLI

The @neural-ng/theme executable currently requires Node.js 24.x.

Browser support follows Angular's baseline

NeuralNg targets the modern browser baseline supported by its Angular major. Chrome, Edge, Firefox and Safari are covered only while their versions fall inside that Angular baseline. Internet Explorer and legacy engines are outside the support contract.

Evergreen desktop browsers

Keyboard, pointer, responsive layout, overlays and forms are expected to work inside Angular’s supported baseline.

Mobile browsers

Responsive and touch behavior follows the matching Safari and Chromium baseline.

SSR environments

Initial rendering must not require window, document, observers or layout measurement.

Embedded webviews

Supported only when the engine satisfies the same feature baseline; product names alone are not enough.

CSS features provided by a consumer theme remain the theme author's responsibility in unstyled mode. Component semantics and state do not depend on Tailwind CSS.

Release channel and component maturity are separate

A component's Beta badge describes its local API maturity inside the project. It does not mean a beta npm package has already been published. The first public package is still planned for the alpha channel.

Integration testing

Alpha

Public APIs may still change as real projects expose missing contracts.

Release candidate surface

Beta

Feature-complete direction with focused fixes and documented breaking changes.

Production contract

Stable

SemVer governs breaking changes and compatibility claims are release requirements.

Semantic versioning begins with publication

Before the first public release, the repository is free to correct names and contracts directly. Once packages are published, version changes communicate consumer impact.

PATCHFixes behavior without changing the documented public contract.

MINORAdds backward-compatible APIs, components or capabilities.

MAJORRemoves or changes a stable public contract, or drops a supported platform line.

PRERELEASEAlpha and beta identifiers may contain breaking refinements before stable.

Read the manifest as the source of truth

A blog post, generated answer or “works on my machine” report does not widen support. The installed package's peer dependencies, engines, release notes and this matrix define the public boundary for that release.

Do not use --force to hide an Angular peer mismatch.
Do not assume a future Angular major is compatible because compilation starts.
Report the exact NeuralNg, Angular, Node and browser versions with a reproduction.
Treat experimental themes separately from Core runtime compatibility.

Primary

Surface