@exhaustive-ui/mcp 22.0.0 → 22.1.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/data/components.json +113 -7
- package/data/llms-full.txt +261 -17
- package/data/llms.txt +2 -0
- package/data/manifest.json +1 -1
- package/data/pages/contribution.md +5 -0
- package/data/pages/faq.md +6 -1
- package/data/pages/installation.md +9 -8
- package/data/pages/optimus.md +107 -0
- package/data/pages/philosophy.md +1 -2
- package/data/pages/primeng.md +120 -0
- package/data/pages/update.md +2 -2
- package/data/pages/v22.md +7 -4
- package/data/snapshot.json +3 -3
- package/dist/index.mjs +2 -2
- package/dist/index.mjs.map +1 -1
- package/package.json +1 -1
package/data/pages/faq.md
CHANGED
|
@@ -41,12 +41,17 @@ Angular v22: ExhaustiveUI v22 requires Angular v22. Our majors follow Angular's
|
|
|
41
41
|
|
|
42
42
|
Mostly, but not through `ng add`, which only sets up new projects and fails without changing anything when it finds an existing `primeng` dependency. Install `@exhaustive-ui/core`, then run
|
|
43
43
|
`ng generate @exhaustive-ui/core:migrate-from-primeng` in a PrimeNG v21 workspace updated to Angular v22: packages swapped, imports rewritten, dependencies installed. It then prints a report of anything it could not rewrite,
|
|
44
|
-
with file and line numbers. The [migration guide](https://
|
|
44
|
+
with file and line numbers. The [migration guide](https://exhaustive-ui.com/migration/primeng) covers the details and the manual cases.
|
|
45
45
|
|
|
46
46
|
### I am on PrimeNG v20 or older. Can I migrate directly?
|
|
47
47
|
|
|
48
48
|
No. Upgrade to PrimeNG v21 first, using PrimeNG's own migration guides, then update Angular to v22 and run the schematic. The schematic checks the version and refuses rather than producing a half-migrated workspace.
|
|
49
49
|
|
|
50
|
+
### I use Optimus UI. Can I switch?
|
|
51
|
+
|
|
52
|
+
Yes. ExhaustiveUI is a fork of Optimus UI, with the same components. On Optimus UI v2, run `ng generate @exhaustive-ui/core:migrate-from-optimus`: packages swapped, imports and configuration API renamed, CSS layer renamed,
|
|
53
|
+
dependencies installed. The [Optimus UI migration guide](https://exhaustive-ui.com/migration/optimus) covers the steps and the v22 migrations that follow.
|
|
54
|
+
|
|
50
55
|
### What happens to my PrimeNG license?
|
|
51
56
|
|
|
52
57
|
Nothing — it is unrelated. A PrimeNG v22 commercial license covers PrimeNG. ExhaustiveUI needs no license at all. If you hold a PrimeTek subscription for their templates or theme designer, those remain their products and do not carry
|
|
@@ -10,8 +10,9 @@ ExhaustiveUI v22 targets Angular v22. Any workspace created with the Angular CLI
|
|
|
10
10
|
- RxJS v7.8.1 or newer
|
|
11
11
|
- A package manager of your choice — npm, yarn or pnpm
|
|
12
12
|
|
|
13
|
-
Already using PrimeNG? Do not follow this page. The [migration guide](https://
|
|
14
|
-
|
|
13
|
+
Already using PrimeNG? Do not follow this page. The [migration guide](https://exhaustive-ui.com/migration/primeng) covers moving an existing PrimeNG v21 workspace, once updated to Angular v22, across with the
|
|
14
|
+
`migrate-from-primeng` schematic, which is a separate command from the `ng add` below. On Optimus UI v2, follow the [Optimus UI migration guide](https://exhaustive-ui.com/migration/optimus) and its
|
|
15
|
+
`migrate-from-optimus` schematic instead.
|
|
15
16
|
|
|
16
17
|
## Angular Version Compatibility
|
|
17
18
|
|
|
@@ -44,10 +45,10 @@ ng add @exhaustive-ui/core --skip-install
|
|
|
44
45
|
ng add @exhaustive-ui/core --project=admin
|
|
45
46
|
```
|
|
46
47
|
|
|
47
|
-
If the schematic cannot find a providers array to update it prints the three manual steps instead of guessing, so nothing in your workspace is rewritten unexpectedly. If it detects an existing `primeng`
|
|
48
|
-
nothing and fails with an error rather than reporting success, and points you at the
|
|
49
|
-
|
|
50
|
-
migration schematic needs it there.
|
|
48
|
+
If the schematic cannot find a providers array to update it prints the three manual steps instead of guessing, so nothing in your workspace is rewritten unexpectedly. If it detects an existing `primeng` or
|
|
49
|
+
`@openng/optimus-ui` dependency it changes nothing and fails with an error rather than reporting success, and points you at the `migrate-from-primeng` or `migrate-from-optimus` schematic, described in the
|
|
50
|
+
[PrimeNG](https://exhaustive-ui.com/migration/primeng) and [Optimus UI](https://exhaustive-ui.com/migration/optimus) migration guides. It does not run that schematic for you. The Angular CLI installs
|
|
51
|
+
`@exhaustive-ui/core` before the schematic runs, so the dependency stays in your `package.json` — the migration schematic needs it there.
|
|
51
52
|
|
|
52
53
|
## Download
|
|
53
54
|
|
|
@@ -87,8 +88,8 @@ export const appConfig: ApplicationConfig = {
|
|
|
87
88
|
|
|
88
89
|
## Icons
|
|
89
90
|
|
|
90
|
-
ExhaustiveUI components
|
|
91
|
-
[OpenNG Icons](https://exhaustive-ui.com/icons)
|
|
91
|
+
ExhaustiveUI components ship their own SVG icons, so an icon library is optional: install one only for the icons you add yourself, through an `icon` input or a template. Every example in this documentation uses the
|
|
92
|
+
`pi pi-{icon}` classes from [OpenNG Icons](https://exhaustive-ui.com/icons); install it if you want the demos to look the way they do here.
|
|
92
93
|
|
|
93
94
|
```bash
|
|
94
95
|
npm install @openng/icons
|
|
@@ -0,0 +1,107 @@
|
|
|
1
|
+
# Migrating from Optimus UI
|
|
2
|
+
|
|
3
|
+
Moving an Optimus UI v2 application to ExhaustiveUI: package and configuration API renames, the CSS layer name, then the v22 migrations.
|
|
4
|
+
|
|
5
|
+
## Overview
|
|
6
|
+
|
|
7
|
+
ExhaustiveUI is a fork of Optimus UI, itself the MIT continuation of PrimeNG v21. An Optimus UI v2 application already runs on Angular 22 and uses the same components, selectors, CSS classes, design tokens and
|
|
8
|
+
`@openng/icons` icons. Moving it across takes two steps:
|
|
9
|
+
|
|
10
|
+
1. **The rename**: the `@openng/optimus-ui*` packages become `@exhaustive-ui/*`, and the four names of the configuration API change. The `migrate-from-optimus` schematic does it.
|
|
11
|
+
2. **The v22 changes**: the Signals API everywhere, OnPush and the API cleanup of ExhaustiveUI v22. The `ng update` migrations do most of it, and the [migration guide to v22](https://exhaustive-ui.com/migration/v22) covers the rest.
|
|
12
|
+
|
|
13
|
+
## Before you start
|
|
14
|
+
|
|
15
|
+
- **Optimus UI v2 on Angular 22.** An application still on Optimus UI v1 updates to v2 first, following Optimus UI's documentation.
|
|
16
|
+
- **A clean git working tree**, so the rename and the migrations can be reviewed on their own, and a build and test run that passes before you start.
|
|
17
|
+
|
|
18
|
+
## Migration steps
|
|
19
|
+
|
|
20
|
+
1. Install ExhaustiveUI and run the `migrate-from-optimus` schematic. It rewrites the workspace, then installs the new dependencies.
|
|
21
|
+
2. Run the v22 migrations. The workspace did not go through `ng update`, so they are run explicitly, from the version before v22.
|
|
22
|
+
3. Read both reports, fix the compiler errors, then build and run your tests.
|
|
23
|
+
|
|
24
|
+
```bash
|
|
25
|
+
npm install @exhaustive-ui/core@22
|
|
26
|
+
ng generate @exhaustive-ui/core:migrate-from-optimus
|
|
27
|
+
ng update @exhaustive-ui/core --migrate-only --from=3.0.0
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
The schematic checks that `@openng/optimus-ui` v2 is installed. It takes two options: `--skip-install` leaves the install to you, and `--force` skips the version check. Like `ng update`, run it on a clean
|
|
31
|
+
working tree so its changes can be reviewed with `git diff`.
|
|
32
|
+
|
|
33
|
+
## What the schematic changes
|
|
34
|
+
|
|
35
|
+
The schematic visits every file of the workspace except `node_modules`, build output and the files your `.gitignore` excludes.
|
|
36
|
+
|
|
37
|
+
### Dependencies
|
|
38
|
+
|
|
39
|
+
In every `package.json` of the workspace, each package is replaced by its counterpart, which has the same content and the same subpaths:
|
|
40
|
+
|
|
41
|
+
- `@openng/optimus-ui` becomes `@exhaustive-ui/core`
|
|
42
|
+
- `@openng/optimus-ui-themes`, `-tailwindcss`, `-locale`, `-styled`, `-styles`, `-utils` and `-motion` become `@exhaustive-ui/themes`, `tailwindcss`, `locale`, `styled`, `styles`, `utils` and `motion`
|
|
43
|
+
- `@openng/icons` stays: ExhaustiveUI uses the same icon set.
|
|
44
|
+
|
|
45
|
+
### TypeScript
|
|
46
|
+
|
|
47
|
+
Imports, dynamic imports and `require()` calls are rewritten, subpaths included (`@openng/optimus-ui/button` becomes `@exhaustive-ui/core/button`), and so is the Tailwind CSS configuration file. The
|
|
48
|
+
configuration API is renamed where it is imported from Optimus UI, along with every use in the file: `provideOptimus` becomes `provideExhaustive`, the `Optimus` service becomes `Exhaustive`,
|
|
49
|
+
`OptimusConfigType` becomes `ExhaustiveConfigType` and `OPTIMUS_CONFIG` becomes `EXHAUSTIVE_CONFIG`. A class of your own that happens to be named `Optimus` is left alone.
|
|
50
|
+
|
|
51
|
+
```typescript
|
|
52
|
+
// Before
|
|
53
|
+
import { ApplicationConfig } from '@angular/core';
|
|
54
|
+
import { provideOptimus } from '@openng/optimus-ui/config';
|
|
55
|
+
import Aura from '@openng/optimus-ui-themes/aura';
|
|
56
|
+
|
|
57
|
+
export const appConfig: ApplicationConfig = {
|
|
58
|
+
providers: [provideOptimus({ theme: { preset: Aura } })]
|
|
59
|
+
};
|
|
60
|
+
|
|
61
|
+
// After
|
|
62
|
+
import { ApplicationConfig } from '@angular/core';
|
|
63
|
+
import { provideExhaustive } from '@exhaustive-ui/core/config';
|
|
64
|
+
import Aura from '@exhaustive-ui/themes/aura';
|
|
65
|
+
|
|
66
|
+
export const appConfig: ApplicationConfig = {
|
|
67
|
+
providers: [provideExhaustive({ theme: { preset: Aura } })]
|
|
68
|
+
};
|
|
69
|
+
```
|
|
70
|
+
|
|
71
|
+
### Stylesheets and angular.json
|
|
72
|
+
|
|
73
|
+
`@import`, `@use`, `@plugin` and `url()` references in stylesheets, and the `styles` and `scripts` entries of `angular.json` and `project.json`, follow the new package names.
|
|
74
|
+
|
|
75
|
+
### The report
|
|
76
|
+
|
|
77
|
+
The schematic ends with the places that still mention `optimus-ui`, `Optimus`, `provideOptimus`, `OptimusConfigType` or `OPTIMUS_CONFIG`, with the file and line: templates, Markdown, comments, or module paths
|
|
78
|
+
passed to other functions, such as `jest.mock()`. Lockfiles are left out, since the install regenerates them.
|
|
79
|
+
|
|
80
|
+
## CSS layer
|
|
81
|
+
|
|
82
|
+
Optimus UI puts its styles in a CSS cascade layer named `optimus` when the theme enables `cssLayer`; ExhaustiveUI names it `exhaustive`. The schematic renames the `optimus` token in the `cssLayer`
|
|
83
|
+
`name` and `order` of your configuration, then the matching `@layer` declarations and `@import ... layer()` clauses in your stylesheets, so your overrides keep their place in the layer order. With
|
|
84
|
+
`cssLayer: true`, the configuration does not change, and only the stylesheets are renamed.
|
|
85
|
+
|
|
86
|
+
A layer of your own, with another name, is left as it is. The CSS classes (`p-button`...), the design tokens (`--p-primary-color`...) and the icon classes (`pi pi-check`...) do not change.
|
|
87
|
+
|
|
88
|
+
## v22 migrations
|
|
89
|
+
|
|
90
|
+
After `migrate-from-optimus`, run the v22 migrations. The workspace did not go through `ng update`, so they are run explicitly, from the version before v22:
|
|
91
|
+
|
|
92
|
+
```bash
|
|
93
|
+
ng update @exhaustive-ui/core --migrate-only --from=3.0.0
|
|
94
|
+
```
|
|
95
|
+
|
|
96
|
+
They rewrite the templates and code for the inputs, outputs and templates removed or renamed in v22, and for the configuration options that became signals or changed name, such as `inputStyle`, now `inputVariant`. They
|
|
97
|
+
report what they cannot rewrite. The [migration guide to v22](https://exhaustive-ui.com/migration/v22) then covers the code changes: signal inputs, `model()` and signal queries in every component, OnPush change
|
|
98
|
+
detection, and the behavior and type changes.
|
|
99
|
+
|
|
100
|
+
## Checklist
|
|
101
|
+
|
|
102
|
+
- No `@openng/optimus-ui*` package left in any `package.json`, and the report of `migrate-from-optimus` handled.
|
|
103
|
+
- `provideExhaustive`, `Exhaustive`, `ExhaustiveConfigType` and `EXHAUSTIVE_CONFIG` in place of the Optimus names.
|
|
104
|
+
- With a CSS layer configured, your overrides still apply.
|
|
105
|
+
- The v22 migrations run and their report handled.
|
|
106
|
+
- The application compiles and its tests pass, after the code changes of the migration guide to v22.
|
|
107
|
+
|
package/data/pages/philosophy.md
CHANGED
|
@@ -72,8 +72,7 @@ migration schematic, rather than dripping renames across releases.
|
|
|
72
72
|
## PrimeNG and PrimeTek
|
|
73
73
|
|
|
74
74
|
ExhaustiveUI is not affiliated with, endorsed by, or sponsored by PrimeTek. PrimeNG, PrimeFaces, PrimeReact, PrimeVue and PrimeFlex are their trademarks. The rename from the inherited names — the packages, the CSS layer, the icon
|
|
75
|
-
library — is a trademark matter, not a technical one, and it is why we ship a [migration schematic](https://
|
|
76
|
-
asking you to rewrite imports by hand.
|
|
75
|
+
library — is a trademark matter, not a technical one, and it is why we ship a [migration schematic](https://exhaustive-ui.com/migration/primeng) rather than asking you to rewrite imports by hand.
|
|
77
76
|
|
|
78
77
|
References to PrimeNG remain throughout this documentation and the source, and they are deliberate. Attribution is the point: this library is PrimeTek's decade of work plus whatever the community adds on top. Pretending otherwise
|
|
79
78
|
would be both dishonest and useless to anyone trying to find their way around a familiar API.
|
|
@@ -0,0 +1,120 @@
|
|
|
1
|
+
# Migrating from PrimeNG
|
|
2
|
+
|
|
3
|
+
Moving a PrimeNG v21 application to ExhaustiveUI: the migrate-from-primeng schematic, what it changes (packages, imports, configuration API, icons, CSS layer), the manual checks and the v22 migrations.
|
|
4
|
+
|
|
5
|
+
## Overview
|
|
6
|
+
|
|
7
|
+
ExhaustiveUI is an MIT fork of PrimeNG v21, the last PrimeNG release published under the MIT license, by way of Optimus UI. The components, their selectors, the `p-*` CSS classes, the design tokens and the `pi pi-*` icon
|
|
8
|
+
classes are the same, so a PrimeNG v21 application moves across in two parts:
|
|
9
|
+
|
|
10
|
+
1. **The switch**: other package names, a configuration API named after ExhaustiveUI, another icon package and another default CSS layer name. The `migrate-from-primeng` schematic does it.
|
|
11
|
+
2. **The v22 changes**: Angular 22, the Signals API, OnPush and the API cleanup of ExhaustiveUI v22. The `ng update` migrations do most of it, and the [migration guide to v22](https://exhaustive-ui.com/migration/v22) covers the rest.
|
|
12
|
+
|
|
13
|
+
No license is needed. A PrimeTek license or subscription for PrimeNG, its templates or its theme designer does not carry over, and is not required.
|
|
14
|
+
|
|
15
|
+
## Before you start
|
|
16
|
+
|
|
17
|
+
- **PrimeNG v21.** ExhaustiveUI shares its API. On v20 or older, upgrade to v21 first with PrimeNG's own update guides; the schematic checks the installed version and stops otherwise. On PrimeNG v22, the schematic runs, but the features PrimeNG added after v21 have no ExhaustiveUI equivalent: check the compiler errors and the report.
|
|
18
|
+
- **A clean git working tree**, so every change can be reviewed and reverted on its own, and a build and test run that passes before you start.
|
|
19
|
+
- **PrimeFlex**, if the project uses it, is not migrated by this schematic. Run `migrate-from-primeflex` afterwards to move its classes to Tailwind CSS; the schematic reminds you when it finds PrimeFlex.
|
|
20
|
+
|
|
21
|
+
## Migration steps
|
|
22
|
+
|
|
23
|
+
1. Update Angular to 22. PrimeNG v21 declares Angular 21 as its peer dependency, so the Angular CLI refuses the update while `primeng` is installed: pass `--force`. The next step removes `primeng`.
|
|
24
|
+
2. Install ExhaustiveUI and run the `migrate-from-primeng` schematic. It rewrites the workspace, then installs the new dependencies.
|
|
25
|
+
3. Run the v22 migrations. The workspace did not go through `ng update`, so they are run explicitly, from the version before v22.
|
|
26
|
+
4. Read both reports, fix the compiler errors, then build and run your tests.
|
|
27
|
+
|
|
28
|
+
```bash
|
|
29
|
+
ng update @angular/core@22 @angular/cli@22 --force
|
|
30
|
+
npm install @exhaustive-ui/core@22
|
|
31
|
+
ng generate @exhaustive-ui/core:migrate-from-primeng
|
|
32
|
+
ng update @exhaustive-ui/core --migrate-only --from=3.0.0
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
The schematic takes two options: `--skip-install` leaves the install to you, and `--force` skips the PrimeNG version check.
|
|
36
|
+
|
|
37
|
+
## What the schematic changes
|
|
38
|
+
|
|
39
|
+
The schematic visits every file of the workspace except `node_modules`, build output and the files your `.gitignore` excludes.
|
|
40
|
+
|
|
41
|
+
### Dependencies
|
|
42
|
+
|
|
43
|
+
In every `package.json` of the workspace, including `overrides` and `resolutions`, each package is replaced by its counterpart:
|
|
44
|
+
|
|
45
|
+
- `primeng` becomes `@exhaustive-ui/core`
|
|
46
|
+
- `@primeuix/themes`, `@primeuix/styled`, `@primeuix/styles`, `@primeuix/utils` and `@primeuix/motion` become `@exhaustive-ui/themes`, `@exhaustive-ui/styled`, `@exhaustive-ui/styles`, `@exhaustive-ui/utils` and `@exhaustive-ui/motion`
|
|
47
|
+
- `tailwindcss-primeui` becomes `@exhaustive-ui/tailwindcss`
|
|
48
|
+
- `primelocale` becomes `@exhaustive-ui/locale`
|
|
49
|
+
- `primeicons` becomes `@openng/icons`
|
|
50
|
+
|
|
51
|
+
### TypeScript
|
|
52
|
+
|
|
53
|
+
Imports, dynamic imports and `require()` calls are rewritten, subpaths included (`primeng/button` becomes `@exhaustive-ui/core/button`, `@primeuix/themes/aura` becomes
|
|
54
|
+
`@exhaustive-ui/themes/aura`), and so is the Tailwind CSS configuration file. The configuration API is renamed where it is imported: `providePrimeNG` becomes `provideExhaustive`, the `PrimeNG` service becomes
|
|
55
|
+
`Exhaustive`, `PrimeNGConfigType` becomes `ExhaustiveConfigType`, and the `PrimeIcons` constants become `OpenngIcons`.
|
|
56
|
+
|
|
57
|
+
```typescript
|
|
58
|
+
// Before
|
|
59
|
+
import { ApplicationConfig } from '@angular/core';
|
|
60
|
+
import { providePrimeNG } from 'primeng/config';
|
|
61
|
+
import Aura from '@primeuix/themes/aura';
|
|
62
|
+
|
|
63
|
+
export const appConfig: ApplicationConfig = {
|
|
64
|
+
providers: [providePrimeNG({ theme: { preset: Aura } })]
|
|
65
|
+
};
|
|
66
|
+
|
|
67
|
+
// After
|
|
68
|
+
import { ApplicationConfig } from '@angular/core';
|
|
69
|
+
import { provideExhaustive } from '@exhaustive-ui/core/config';
|
|
70
|
+
import Aura from '@exhaustive-ui/themes/aura';
|
|
71
|
+
|
|
72
|
+
export const appConfig: ApplicationConfig = {
|
|
73
|
+
providers: [provideExhaustive({ theme: { preset: Aura } })]
|
|
74
|
+
};
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
### Stylesheets and angular.json
|
|
78
|
+
|
|
79
|
+
`@import`, `@use`, `@plugin` and `url()` references in stylesheets, and the `styles` and `scripts` entries of `angular.json` and `project.json`, follow the new package names.
|
|
80
|
+
`primeicons/primeicons.css` becomes `@openng/icons/openng-icons.css`; the `pi pi-*` classes in templates do not change.
|
|
81
|
+
|
|
82
|
+
### CSS cascade layer
|
|
83
|
+
|
|
84
|
+
When the theme sets `cssLayer`, the `primeng` layer becomes `exhaustive` in its `name` and `order`, `primeng-overwrites` becomes `exhaustive-overwrites`, and the matching
|
|
85
|
+
`@layer` declarations in your stylesheets are renamed too, so your overrides keep their place in the layer order. With `cssLayer: true`, the configuration does not change, and only the stylesheets are renamed.
|
|
86
|
+
|
|
87
|
+
### The report
|
|
88
|
+
|
|
89
|
+
The schematic ends with the places that still mention `primeng`, `primeicons`, `@primeuix`, `tailwindcss-primeui` or `primelocale`, with the file and line: templates, Markdown, JSON or code it does not
|
|
90
|
+
rewrite. Lockfiles are left out of the report, since the install regenerates them.
|
|
91
|
+
|
|
92
|
+
## Manual checks
|
|
93
|
+
|
|
94
|
+
Besides the places listed in the report, check these by hand:
|
|
95
|
+
|
|
96
|
+
- **The icon font name.** A stylesheet that names the font directly, as in `font-family: 'primeicons'`, now needs `'openng-icons'`. The schematic does not touch declaration values.
|
|
97
|
+
- **Local variables named after PrimeNG**, such as `primeng = inject(PrimeNG)`: the type is renamed, the variable name is yours to keep or change.
|
|
98
|
+
- **Module paths passed to other functions**, such as `jest.mock('primeng/button')` or `vi.mock()`: only imports, dynamic imports and `require()` are rewritten. These appear in the report.
|
|
99
|
+
- **Build and deployment files** outside the TypeScript sources and stylesheets: Dockerfiles, CI scripts, CDN links to PrimeNG or PrimeIcons.
|
|
100
|
+
- **PrimeTek products** such as templates or the theme designer are not part of ExhaustiveUI. A preset built with them is a plain `definePreset()` object and keeps working once its imports point to `@exhaustive-ui/themes`.
|
|
101
|
+
|
|
102
|
+
## What changes in v22
|
|
103
|
+
|
|
104
|
+
After the switch, the application runs on ExhaustiveUI v22, which differs from PrimeNG v21 in ways the compiler and your tests will show. The [migration guide to v22](https://exhaustive-ui.com/migration/v22)
|
|
105
|
+
details each of them:
|
|
106
|
+
|
|
107
|
+
- Inputs, two-way properties, outputs and queries are signals: code holding a component instance reads inputs with a call and writes two-way properties with `.set()`.
|
|
108
|
+
- Components use OnPush change detection, except Table, TreeTable and DynamicDialog: give them new arrays and objects, or signals, rather than mutating bound data.
|
|
109
|
+
- Deprecated and inactive inputs are removed or renamed, `styleClass` becomes `class` on most components; the v22 migrations rewrite these bindings and report the rest.
|
|
110
|
+
- Hundreds of bugs inherited from PrimeNG v21 are fixed, each with a regression test; a few of them change a visible behavior.
|
|
111
|
+
|
|
112
|
+
## Checklist
|
|
113
|
+
|
|
114
|
+
- Angular 22 installed, and no `primeng`, `@primeuix/*`, `primeicons`, `tailwindcss-primeui` or `primelocale` left in any `package.json`.
|
|
115
|
+
- The report of `migrate-from-primeng` handled, then the report of the v22 migrations.
|
|
116
|
+
- Icons render: the stylesheet is `@openng/icons/openng-icons.css` and nothing names the `primeicons` font.
|
|
117
|
+
- With a CSS layer configured, your overrides still apply: the `@layer` names match the theme's `cssLayer` order.
|
|
118
|
+
- The application compiles and its tests pass, after the code changes of the migration guide to v22.
|
|
119
|
+
- PrimeFlex, if used, migrated with `migrate-from-primeflex`.
|
|
120
|
+
|
package/data/pages/update.md
CHANGED
|
@@ -9,8 +9,8 @@ new version. ExhaustiveUI supports `ng update`, the Angular CLI's own update mec
|
|
|
9
9
|
|
|
10
10
|
Major versions follow Angular's: when a new Angular major ships, a matching ExhaustiveUI major is released for it. Minor and patch releases stay within the same Angular major and are drop-in updates.
|
|
11
11
|
|
|
12
|
-
This page is about updating a project that already uses ExhaustiveUI. To move an existing
|
|
13
|
-
[migration
|
|
12
|
+
This page is about updating a project that already uses ExhaustiveUI. To move an existing workspace across, see the guides for
|
|
13
|
+
[PrimeNG](https://exhaustive-ui.com/migration/primeng) and [Optimus UI](https://exhaustive-ui.com/migration/optimus) instead.
|
|
14
14
|
|
|
15
15
|
## Updating
|
|
16
16
|
|
package/data/pages/v22.md
CHANGED
|
@@ -40,20 +40,23 @@ Update Angular to 22, install ExhaustiveUI and run the `migrate-from-primeng` sc
|
|
|
40
40
|
`@exhaustive-ui/core/button`) and renames the configuration API (`providePrimeNG` becomes `provideExhaustive`). The workspace did not go through `ng update`, so run the v22 migrations explicitly afterwards.
|
|
41
41
|
|
|
42
42
|
```bash
|
|
43
|
-
ng update @angular/core@22 @angular/cli@22
|
|
43
|
+
ng update @angular/core@22 @angular/cli@22 --force
|
|
44
44
|
npm install @exhaustive-ui/core@22
|
|
45
45
|
ng generate @exhaustive-ui/core:migrate-from-primeng
|
|
46
46
|
ng update @exhaustive-ui/core --migrate-only --from=3.0.0
|
|
47
47
|
```
|
|
48
48
|
|
|
49
|
-
Projects on PrimeNG v20 or older upgrade to PrimeNG v21 first; the schematic checks the version and refuses otherwise.
|
|
49
|
+
Projects on PrimeNG v20 or older upgrade to PrimeNG v21 first; the schematic checks the version and refuses otherwise. The [PrimeNG migration guide](https://exhaustive-ui.com/migration/primeng) details each step,
|
|
50
|
+
including the `--force` the Angular update needs while `primeng` is installed.
|
|
50
51
|
|
|
51
52
|
### From Optimus UI v2
|
|
52
53
|
|
|
53
|
-
Optimus UI v2 has the PrimeNG v21 API under other package names.
|
|
54
|
-
|
|
54
|
+
Optimus UI v2 has the PrimeNG v21 API under other package names. The `migrate-from-optimus` schematic swaps its packages for their `@exhaustive-ui/*` counterparts and renames the imports, the configuration API and the
|
|
55
|
+
CSS layer; then run the v22 migrations explicitly. The [Optimus UI migration guide](https://exhaustive-ui.com/migration/optimus) details each step.
|
|
55
56
|
|
|
56
57
|
```bash
|
|
58
|
+
npm install @exhaustive-ui/core@22
|
|
59
|
+
ng generate @exhaustive-ui/core:migrate-from-optimus
|
|
57
60
|
ng update @exhaustive-ui/core --migrate-only --from=3.0.0
|
|
58
61
|
```
|
|
59
62
|
|
package/data/snapshot.json
CHANGED
|
@@ -1,9 +1,9 @@
|
|
|
1
1
|
{
|
|
2
|
-
"generatedAt": "2026-11-
|
|
3
|
-
"libraryVersion": "22.
|
|
2
|
+
"generatedAt": "2026-11-22T18:24:32.055Z",
|
|
3
|
+
"libraryVersion": "22.1.0",
|
|
4
4
|
"docsGeneratedAt": "2026-11-22",
|
|
5
5
|
"components": 96,
|
|
6
|
-
"guides":
|
|
6
|
+
"guides": 20,
|
|
7
7
|
"source": "local",
|
|
8
8
|
"origin": "../../apps/docs/public/llms"
|
|
9
9
|
}
|
package/dist/index.mjs
CHANGED
|
@@ -2679,8 +2679,8 @@ const PROMPTS = {
|
|
|
2679
2679
|
title: "Migrate from PrimeNG",
|
|
2680
2680
|
description: "Plan the migration of PrimeNG (or Optimus UI) code to ExhaustiveUI.",
|
|
2681
2681
|
steps: [
|
|
2682
|
-
"
|
|
2683
|
-
"
|
|
2682
|
+
"Call get_guide for \"primeng\" (from PrimeNG v21) or \"optimus\" (from Optimus UI v2), and follow its steps.",
|
|
2683
|
+
"From PrimeNG: update Angular to v22 with --force while primeng is installed, then run `ng generate @exhaustive-ui/core:migrate-from-primeng`. From Optimus UI: run `ng generate @exhaustive-ui/core:migrate-from-optimus`. Then run `ng update @exhaustive-ui/core --migrate-only --from=3.0.0` and follow get_guide \"v22\".",
|
|
2684
2684
|
"For each PrimeNG component used, call get_component with the PrimeNG name: renamed components (dropdown, calendar, sidebar, overlaypanel, inputswitch, tabview...) resolve to their ExhaustiveUI equivalent.",
|
|
2685
2685
|
"Replace `primeng/<name>` imports with `@exhaustive-ui/core/<name>` and call validate_usage on each migrated template."
|
|
2686
2686
|
]
|