Neural UI 2 supports Angular 22 only. Keep Angular framework packages aligned and use CDK and schematics from the same major. The table separates Core requirements from the compiler and runtime requirements of Angular.
The concrete verified combination is Angular/CDK 22.2.2, CLI/schematics 22.2.2, TypeScript 6.0.3 and RxJS 7.8.2. Check your installed Angular compiler before changing TypeScript.
Run these commands in the folder containing package.json. node --version must fall within a supported engine range. ng version identifies your framework and tooling. npm ls should not report invalid peers or conflicting Angular majors.
Before installing Core, it is normal for @neural-ui/core not to appear in the dependency tree. After installation, repeat the check to verify the resolved Core 2.x package and its peers.
Terminal
node --version
npx ng version
npm ls @neural-ui/core @angular/core @angular/cdk @angular/cli typescript rxjs
Skip this step if you already have a compatible application. This command creates a standalone Angular application with SCSS. Angular 22 uses zoneless change detection by default. Choose server rendering only if your product needs it; the SSR guide covers that setup.
Terminal
npx @angular/cli@22.2.2 new neural-app --standalone --style=scss --package-manager=npm
cd neural-app
Upgrade the Angular application to a supported Angular 22 toolchain before integrating Core 2. The package currently includes setup and page-generation schematics, but no ng-update migration that automatically rewrites Neural UI 1 templates or forms. ng add is setup, not a migration.
Work on a recoverable branch. Review public entrypoint imports, exact selectors, renamed or removed inputs, model/proposal events, styles and projected templates against each component API. For signal controls, replace legacy ControlValueAccessor formControlName/ngModel bindings with FormField or the documented model. Build, then test real interactions, focus and responsive layout; a dependency upgrade alone does not complete this migration.
Angular 21 or earlier must be upgraded before adding Core 2. Mixed Angular majors and an incompatible TypeScript version should be resolved in the application toolchain, not hidden with --force or --legacy-peer-deps. Install Node separately; it is not an npm application dependency.
A valid version tree is a prerequisite, not proof that your whole application works. Continue with Installation to load styles and render a component.
