@exhaustive-ui/mcp 22.0.0-rc.2 → 22.0.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.
Files changed (62) hide show
  1. package/data/components/accordion.md +1 -0
  2. package/data/components/autocomplete.md +59 -0
  3. package/data/components/cascadeselect.md +136 -0
  4. package/data/components/checkbox.md +56 -0
  5. package/data/components/colorpicker.md +49 -0
  6. package/data/components/confirmpopup.md +0 -7
  7. package/data/components/dataview.md +0 -2
  8. package/data/components/datepicker.md +52 -3
  9. package/data/components/drawer.md +1 -1
  10. package/data/components/editor.md +49 -0
  11. package/data/components/floatlabel.md +72 -0
  12. package/data/components/iftalabel.md +68 -0
  13. package/data/components/inputmask.md +54 -4
  14. package/data/components/inputnumber.md +52 -3
  15. package/data/components/inputotp.md +50 -0
  16. package/data/components/inputtext.md +63 -1
  17. package/data/components/knob.md +55 -0
  18. package/data/components/listbox.md +57 -2
  19. package/data/components/message.md +0 -1
  20. package/data/components/multiselect.md +59 -4
  21. package/data/components/orderlist.md +1 -3
  22. package/data/components/password.md +52 -3
  23. package/data/components/picklist.md +0 -3
  24. package/data/components/radiobutton.md +60 -0
  25. package/data/components/rating.md +49 -0
  26. package/data/components/select.md +58 -3
  27. package/data/components/selectbutton.md +50 -1
  28. package/data/components/slider.md +50 -0
  29. package/data/components/stepper.md +0 -1
  30. package/data/components/table.md +1 -1
  31. package/data/components/textarea.md +48 -0
  32. package/data/components/togglebutton.md +50 -0
  33. package/data/components/toggleswitch.md +49 -0
  34. package/data/components/tooltip.md +0 -1
  35. package/data/components/treeselect.md +61 -1
  36. package/data/components/treetable.md +1 -1
  37. package/data/components.json +774 -503
  38. package/data/llms-full.txt +3494 -819
  39. package/data/llms.txt +2 -1
  40. package/data/manifest.json +91 -476
  41. package/data/pages/accessibility.md +164 -6
  42. package/data/pages/animations.md +110 -5
  43. package/data/pages/configuration.md +107 -102
  44. package/data/pages/contribution.md +68 -7
  45. package/data/pages/customicons.md +8 -8
  46. package/data/pages/faq.md +103 -8
  47. package/data/pages/icons.md +24 -23
  48. package/data/pages/installation.md +77 -25
  49. package/data/pages/llms.md +71 -15
  50. package/data/pages/passthrough.md +96 -7
  51. package/data/pages/philosophy.md +80 -11
  52. package/data/pages/primeflex.md +41 -4
  53. package/data/pages/rtl.md +4 -1
  54. package/data/pages/styled.md +174 -66
  55. package/data/pages/tailwind.md +309 -218
  56. package/data/pages/unstyled.md +48 -7
  57. package/data/pages/update.md +42 -13
  58. package/data/pages/v22.md +218 -0
  59. package/data/snapshot.json +4 -4
  60. package/dist/index.mjs +72 -22
  61. package/dist/index.mjs.map +1 -1
  62. package/package.json +1 -1
@@ -4,29 +4,118 @@ Pass Through Props allow direct access to the underlying elements for complete c
4
4
 
5
5
  ## Basic
6
6
 
7
- Each component has a special pt property to define an object with keys corresponding to the available DOM elements. Each value can either be a string, an object or a function that returns a string or an object to define the arbitrary properties to apply to the element such as styling, aria, data-* or custom attributes. If the value is a string or a function that returns a string, it is considered as a class definition and added to the class attribute of the element. Every component documentation has a dedicated section to document the available section names exposed via PT.
7
+ Each component has a special `pt` property to define an object with keys corresponding to the available DOM elements. Each value can either be a string, an object or a function that returns a string or an object to define the
8
+ arbitrary properties to apply to the element such as styling, aria, data-* or custom attributes. If the value is a string or a function that returns a string, it is considered as a class definition and added to the class attribute of
9
+ the element. Every component documentation has a dedicated section to document the available section names exposed via PT.
8
10
 
9
11
  ## Global
10
12
 
11
- PassThrough object can also be defined at a global level to apply all components in an application using the provideExhaustive provider. For example, with the configuration here all panel headers have the bg-primary style class and all autocomplete components have a fixed width. These settings can be overridden by a particular component as components pt property has higher precedence over global pt by default.
13
+ PassThrough object can also be defined at a global level to apply all components in an application using the `provideExhaustive` provider. For example, with the configuration here all panel headers have the
14
+ `bg-primary` style class and all autocomplete components have a fixed width. These settings can be overridden by a particular component as components `pt` property has higher precedence over global `pt` by default.
12
15
 
13
16
  ## Instance
14
17
 
15
- In cases where you need to access the UI Component instance, define a component passthrough type that exposes the component instance or a function that receives a PassThroughContext as parameter.
18
+ In cases where you need to access the UI Component instance, define a component passthrough type that exposes the component instance or a function that receives a `PassThroughContext` as parameter.
16
19
 
17
20
  ## Introduction
18
21
 
19
- In traditional 3rd party UI libraries, users are limited to the API provided by component author. This API commonly consists of inputs, outputs, and content projection. Whenever a requirement emerges for a new customization option in the API, the component author needs to develop and publish it with a new release. The pass through feature is a key element to implement this vision by exposing the component internals in order to apply arbitrary attributes and listeners to the DOM elements. The primary advantage of this approach is that it frees you from being restricted by the main component API. We recommend considering the pass-through feature whenever you need to tailor a component that lacks a built-in feature for your specific requirement. Each component has a special pt property to define an object with keys corresponding to the available DOM elements. A value of a key can either be a string, an object or a function to define the arbitrary properties such as styling, aria, data-* or custom attributes for the element. If the value is a string or a function that returns a string, it serves as a shorthand for a style class definition. Every component documentation has a dedicated segment to document the available section names in the interactive PT Viewer. Panel Example In this example, a Panel is customized with various options through pt . The styling is overriden with Tailwind CSS and header receives custom attributes along with a click event. The attributes passed to the header are not available in the component API, thanks to PassThrough feature, this is no longer an issue as you are not limited to the component api. Note that, you may avoid the ! based overrides in Tailwind classes if you setup CSS Layers with ExhaustiveUI. Visit the Override section at Tailwind integration for examples.
22
+ In traditional 3rd party UI libraries, users are limited to the API provided by component author. This API commonly consists of inputs, outputs, and content projection. Whenever a requirement emerges for a new customization option in
23
+ the API, the component author needs to develop and publish it with a new release.
24
+
25
+ The pass through feature is a key element to implement this vision by exposing the component internals in order to apply arbitrary attributes and listeners to the DOM elements. The primary advantage of this approach is that it frees
26
+ you from being restricted by the main component API. We recommend considering the pass-through feature whenever you need to tailor a component that lacks a built-in feature for your specific requirement.
27
+
28
+ Each component has a special `pt` property to define an object with keys corresponding to the available DOM elements. A value of a key can either be a string, an object or a function to define the arbitrary properties such as
29
+ styling, aria, data-* or custom attributes for the element. If the value is a string or a function that returns a string, it serves as a shorthand for a style class definition. Every component documentation has a dedicated segment to
30
+ document the available section names in the interactive PT Viewer.
31
+
32
+ ### Panel Example
33
+
34
+ In this example, a Panel is customized with various options through `pt`. The styling is overriden with Tailwind CSS and header receives custom attributes along with a click event. The attributes passed to the header are not
35
+ available in the component API, thanks to PassThrough feature, this is no longer an issue as you are not limited to the component api. Note that, you may avoid the `!` based overrides in Tailwind classes if you setup CSS Layers
36
+ with ExhaustiveUI. Visit the [Override](https://exhaustive-ui.com/tailwind) section at Tailwind integration for examples.
20
37
 
21
38
  ## Lifecycle
22
39
 
23
- Lifecycle hooks of components are exposed as pass through using the hooks property so that callback functions can be registered. Available callbacks are onBeforeInit , onInit , onChanges , onDoCheck , onAfterContentInit , onAfterContentChecked , onAfterViewInit , onAfterViewChecked and onDestroy . Refer to the Angular documentation for detailed information about lifecycle hooks.
40
+ Lifecycle hooks of components are exposed as pass through using the `hooks` property so that callback functions can be registered. Available callbacks are `onBeforeInit`, `onInit`, `onChanges`, `onDoCheck`,
41
+ `onAfterContentInit`, `onAfterContentChecked`, `onAfterViewInit`, `onAfterViewChecked` and `onDestroy`. Refer to the Angular documentation for detailed information about lifecycle hooks.
24
42
 
25
43
  ## Pcprefix
26
44
 
27
- A UI component may also use other UI components, in this case section names are prefixed with pc (Prime Component) to denote the ExhaustiveUI component begin used. This distinguishes components from standard DOM elements and indicating the necessity for a nested structure. For example, the badge section is identified as pcBadge because the button component incorporates the badge component internally.
45
+ A UI component may also use other UI components, in this case section names are prefixed with `pc` (Prime Component) to denote the ExhaustiveUI component begin used. This distinguishes components from standard DOM elements and
46
+ indicating the necessity for a nested structure. For example, the `badge` section is identified as `pcBadge` because the button component incorporates the badge component internally.
28
47
 
29
48
  ## Ptoptions
30
49
 
31
- The ⁠ptOptions property determines how a component's local PassThrough configuration merges with the global PT configuration, as demonstrated in the following examples using both global and component-level settings. The mergeSections defines whether the sections from the main configuration gets added and the mergeProps controls whether to override or merge the defined props. Defaults are true for mergeSections and false for mergeProps . Global Configuration mergeSections: true, mergeProps: false (default) mergeSections: true, mergeProps: true mergeSections: false, mergeProps: true mergeSections: false, mergeProps: false
50
+ The `⁠ptOptions` property determines how a component's local PassThrough configuration merges with the global PT configuration, as demonstrated in the following examples using both global and component-level settings.
51
+
52
+ The `mergeSections` defines whether the sections from the main configuration gets added and the `mergeProps` controls whether to override or merge the defined props. Defaults are `true` for `mergeSections` and
53
+ `false` for `mergeProps`.
54
+
55
+ ### Global Configuration
56
+
57
+ ```typescript
58
+ import { ApplicationConfig } from '@angular/core';
59
+ import { provideExhaustive } from '@exhaustive-ui/core/config';
60
+
61
+ export const appConfig: ApplicationConfig = {
62
+ providers: [
63
+ provideExhaustive({
64
+ pt: {
65
+ panel: {
66
+ header: {
67
+ 'data-custom': 'acme-panel',
68
+ class: 'bg-primary text-primary-contrast'
69
+ },
70
+ content: 'font-medium'
71
+ }
72
+ }
73
+ })
74
+ ]
75
+ };
76
+ ```
77
+
78
+ ### mergeSections: true, mergeProps: false (default)
79
+
80
+ ```typescript
81
+ import { Component } from '@angular/core';
82
+ import { Panel, PanelModule, PanelPassThrough } from '@exhaustive-ui/core/panel';
83
+
84
+ @Component({
85
+ selector: 'ptoptions-doc',
86
+ template: \
87
+ ```
88
+
89
+ ### mergeSections: true, mergeProps: true
90
+
91
+ ```typescript
92
+ import { Component } from '@angular/core';
93
+ import { Panel, PanelModule, PanelPassThrough } from '@exhaustive-ui/core/panel';
94
+
95
+ @Component({
96
+ selector: 'ptoptions-doc',
97
+ template: \
98
+ ```
99
+
100
+ ### mergeSections: false, mergeProps: true
101
+
102
+ ```typescript
103
+ import { Component } from '@angular/core';
104
+ import { Panel, PanelModule, PanelPassThrough } from '@exhaustive-ui/core/panel';
105
+
106
+ @Component({
107
+ selector: 'ptoptions-doc',
108
+ template: \
109
+ ```
110
+
111
+ ### mergeSections: false, mergeProps: false
112
+
113
+ ```typescript
114
+ import { Component } from '@angular/core';
115
+ import { Panel, PanelModule, PanelPassThrough } from '@exhaustive-ui/core/panel';
116
+
117
+ @Component({
118
+ selector: 'ptoptions-doc',
119
+ template: \
120
+ ```
32
121
 
@@ -2,27 +2,96 @@
2
2
 
3
3
  Why ExhaustiveUI exists, what it commits to, and where it stops.
4
4
 
5
- ## Governance
5
+ ## Why This Fork Exists
6
6
 
7
- Everything happens in the open, in the repository . There is no private roadmap and no internal issue tracker. What you see in the issues, the discussions and the roadmap is the whole plan. Contributors earn commit access by contributing — the contribution guide describes the Contributor and Committer roles and roughly what it takes to reach them. We would rather grow the number of people who can merge a fix than route everything through one person. Breaking changes are avoided within a major and documented when a major requires them. Where we inherited a name that no longer fits — the CSS cascade layer, the package scope, the icon library — we changed it once, at v1, with a migration schematic, rather than dripping renames across releases.
7
+ In June 2026 PrimeTek archived the PrimeNG repository and moved future major versions, starting with v22, to a commercial license. They explained their reasoning in
8
+ [their own announcement](https://primeui.dev/nextchapter), and it is worth reading. Maintaining a component library of this size for a decade, largely for free, is genuinely hard,
9
+ and we do not think the decision was made lightly.
8
10
 
9
- ## Limits
11
+ It did, however, leave a lot of applications on a library with no further open source releases. ExhaustiveUI exists for those applications. It is a community fork of the last MIT licensed version of PrimeNG, v21, and it stays MIT.
10
12
 
11
- Naming the limits is what makes the commitments above worth anything. Here is what ExhaustiveUI is not. There is no commercial support No SLA, no support contract, no guaranteed response time. Issues and discussions are answered by volunteers when they have time. If your organisation needs contractual guarantees, this project cannot provide them and you should plan accordingly. There are no premium templates, blocks or design tooling PrimeTek's application templates, block library and visual theme designer are their commercial products. They are not part of what was MIT licensed, so they are not part of this fork and will not be reimplemented. Theming here means editing preset objects in code, which is documented in full. We are not chasing feature parity with PrimeNG v22 and beyond PrimeNG continues under its own license and its own roadmap. ExhaustiveUI diverges from v21 forward. Some things they add, we will not have. Some things we fix, they will not. Treat the two as separate libraries that share an ancestor, not as a free copy of a paid product. The bus factor is real This is maintained by a small group of people in their own time. We would rather say that plainly than imply a larger organisation stands behind it. The best way to change that number is to contribute .
13
+ This is not an official fork and it is not endorsed by PrimeTek. It is a separate repository, seeded with PrimeNG's code and history, maintained by people who depend on it.
12
14
 
13
- ## Origin
15
+ ## What We Commit To
14
16
 
15
- In June 2026 PrimeTek archived the PrimeNG repository and moved future major versions, starting with v22, to a commercial license. They explained their reasoning in their own announcement , and it is worth reading. Maintaining a component library of this size for a decade, largely for free, is genuinely hard, and we do not think the decision was made lightly. It did, however, leave a lot of applications on a library with no further open source releases. ExhaustiveUI exists for those applications. It is a community fork of the last MIT licensed version of PrimeNG, v21, and it stays MIT. This is not an official fork and it is not endorsed by PrimeTek. It is a separate repository, seeded with PrimeNG's code and history, maintained by people who depend on it.
17
+ Four commitments, in the order we would want to read them if we were choosing a dependency:
16
18
 
17
- ## Promises
19
+ ### MIT, with no second tier
18
20
 
19
- Four commitments, in the order we would want to read them if we were choosing a dependency: MIT, with no second tier Every package we publish is MIT licensed. There is no paid edition, no enterprise build, no feature held back behind a subscription, and no plan to introduce one. If that ever changed, it would be a fork of this project rather than a relicensing of it, because the code we inherited is MIT and so is everything we add to it. We track Angular Our release cadence follows Angular's. When a new Angular major lands, the priority is a compatible ExhaustiveUI major — before new features, before refactors. Staying upgradeable is the single most valuable thing a component library can do for the applications built on it. Bugs before features We inherited a large backlog along with the code. Fixing what is broken ranks above adding what is missing. Feature requests are triaged and welcome, but they generally ship when someone in the community implements them. No surprises in your bundle The library sends no telemetry, phones no home, and requires no account or key to use. What you install is what runs.
21
+ Every package we publish is MIT licensed. There is no paid edition, no enterprise build, no feature held back behind a subscription, and no plan to introduce one. If that ever changed, it would be a fork of this project rather than a
22
+ relicensing of it, because the code we inherited is MIT and so is everything we add to it.
23
+
24
+ ### We track Angular
25
+
26
+ Our release cadence follows Angular's. When a new Angular major lands, the priority is a compatible ExhaustiveUI major — before new features, before refactors. Staying upgradeable is the single most valuable thing a component library
27
+ can do for the applications built on it.
28
+
29
+ ### Bugs before features
30
+
31
+ We inherited a large backlog along with the code. Fixing what is broken ranks above adding what is missing. Feature requests are triaged and welcome, but they generally ship when someone in the community implements them.
32
+
33
+ ### No surprises in your bundle
34
+
35
+ The library sends no telemetry, phones no home, and requires no account or key to use. What you install is what runs.
36
+
37
+ ## What We Do Not Do
38
+
39
+ Naming the limits is what makes the commitments above worth anything. Here is what ExhaustiveUI is not.
40
+
41
+ ### There is no commercial support
42
+
43
+ No SLA, no support contract, no guaranteed response time. Issues and discussions are answered by volunteers when they have time. If your organisation needs contractual guarantees, this project cannot provide them and you should plan
44
+ accordingly.
45
+
46
+ ### There are no premium templates, blocks or design tooling
47
+
48
+ PrimeTek's application templates, block library and visual theme designer are their commercial products. They are not part of what was MIT licensed, so they are not part of this fork and will not be reimplemented. Theming here means
49
+ editing preset objects in code, which is documented in full.
50
+
51
+ ### We are not chasing feature parity with PrimeNG v22 and beyond
52
+
53
+ PrimeNG continues under its own license and its own roadmap. ExhaustiveUI diverges from v21 forward. Some things they add, we will not have. Some things we fix, they will not. Treat the two as separate libraries that share an
54
+ ancestor, not as a free copy of a paid product.
55
+
56
+ ### The bus factor is real
57
+
58
+ This is maintained by a small group of people in their own time. We would rather say that plainly than imply a larger organisation stands behind it. The best way to change that number is to
59
+ [contribute](https://github.com/e-xiste/exhaustive-ui).
60
+
61
+ ## How Decisions Are Made
62
+
63
+ Everything happens in the open, in the [repository](https://github.com/e-xiste/exhaustive-ui). There is no private roadmap and no internal issue tracker. What you see in the issues,
64
+ the discussions and the [roadmap](https://exhaustive-ui.com/roadmap) is the whole plan.
65
+
66
+ Contributors earn commit access by contributing — the [contribution guide](https://exhaustive-ui.com/contribution) describes the Contributor and Committer roles and roughly what it takes to reach them. We would rather
67
+ grow the number of people who can merge a fix than route everything through one person.
68
+
69
+ Breaking changes are avoided within a major and documented when a major requires them. Where we inherited a name that no longer fits — the CSS cascade layer, the package scope, the icon library — we changed it once, at v1, with a
70
+ migration schematic, rather than dripping renames across releases.
71
+
72
+ ## PrimeNG and PrimeTek
73
+
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://v1.optimus.openng.org/migration/primeng) rather than
76
+ asking you to rewrite imports by hand.
77
+
78
+ 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
+ would be both dishonest and useless to anyone trying to find their way around a familiar API.
80
+
81
+ The code we forked was published under the MIT license, and we distribute it under those same terms, with the original copyright notices intact.
20
82
 
21
83
  ## Sustainability
22
84
 
23
- The honest answer to "how is this funded" is: it mostly is not. e-xiste covers the hosting and the domain; the work is volunteered. That is a fragile arrangement, and it is the main risk to this project — larger than any technical risk we can see today. The things that actually help, roughly in order of impact: Reproducing and triaging issues. A bug with a minimal reproduction is several times more likely to get fixed. Sending pull requests, especially for issues labelled help-needed . Answering questions in discussions, so the same answer is not written five times. Improving this documentation. Every page has a source file and every fix is welcome. Telling your employer you depend on it. Sponsored maintenance time is worth more than any one-off donation. The contribution guide covers how to get started.
85
+ The honest answer to "how is this funded" is: it mostly is not. e-xiste covers the hosting and the domain; the work is volunteered. That is a fragile arrangement, and it is the main risk to this project — larger than any technical
86
+ risk we can see today.
87
+
88
+ The things that actually help, roughly in order of impact:
24
89
 
25
- ## Trademark
90
+ - Reproducing and triaging issues. A bug with a minimal reproduction is several times more likely to get fixed.
91
+ - Sending pull requests, especially for issues labelled `help-needed`.
92
+ - Answering questions in discussions, so the same answer is not written five times.
93
+ - Improving this documentation. Every page has a source file and every fix is welcome.
94
+ - Telling your employer you depend on it. Sponsored maintenance time is worth more than any one-off donation.
26
95
 
27
- 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 library — is a trademark matter, not a technical one, and it is why we ship a migration schematic rather than asking you to rewrite imports by hand. 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 would be both dishonest and useless to anyone trying to find their way around a familiar API. The code we forked was published under the MIT license, and we distribute it under those same terms, with the original copyright notices intact.
96
+ The [contribution guide](https://exhaustive-ui.com/contribution) covers how to get started.
28
97
 
@@ -4,17 +4,54 @@ Moving from PrimeFlex to Tailwind CSS.
4
4
 
5
5
  ## Compatibility
6
6
 
7
- If you are staying on PrimeFlex for now, ExhaustiveUI pairs with PrimeFlex v4 — the same combination that worked with PrimeNG v18 and newer, since the styling architecture is unchanged. PrimeFlex v3 targeted the older PrimeNG releases and is not a supported pairing here. Neither version is tested against ExhaustiveUI releases, so treat this as "should work", not as a supported configuration. The migration below is the path we actually maintain.
7
+ If you are staying on PrimeFlex for now, ExhaustiveUI pairs with PrimeFlex v4 — the same combination that worked with PrimeNG v18 and newer, since the styling architecture is unchanged. PrimeFlex v3 targeted the older PrimeNG releases
8
+ and is not a supported pairing here.
9
+
10
+ Neither version is tested against ExhaustiveUI releases, so treat this as "should work", not as a supported configuration. The migration below is the path we actually maintain.
8
11
 
9
12
  ## Migration
10
13
 
11
- PrimeFlex class names map closely onto Tailwind's, so most of the work is mechanical. PrimeTek's primeclt ships a pf2tw command that does the conversion, and it works on any codebase — it rewrites class names and does not care which component library you use. Run pf2tw in a directory containing the files to convert. pf2tw was written for Tailwind v3. Tailwind v4 renamed a few of the utilities it produces, for example shadow-sm to shadow-xs , rounded to rounded-sm and flex-grow to grow . On Tailwind v4, check the converted classes against the renamed utilities list of the Tailwind upgrade guide. A handful of PrimeFlex classes have no Tailwind counterpart and are left alone. Replace them with flexbox or grid utilities by hand: formgrid formgroup formgroup-inline col col-fixed field field-checkbox field-radiobutton reset
14
+ PrimeFlex class names map closely onto Tailwind's, so most of the work is mechanical. PrimeTek's
15
+ [primeclt](https://www.npmjs.com/package/primeclt) ships a `pf2tw` command that does the conversion, and it works on any codebase — it rewrites class names and does not care
16
+ which component library you use.
17
+
18
+ ```bash
19
+ npm install -g primeclt
20
+ ```
21
+
22
+ Run `pf2tw` in a directory containing the files to convert.
23
+
24
+ ```bash
25
+ prime pf2tw
26
+ ```
27
+
28
+ `pf2tw` was written for Tailwind v3. Tailwind v4 renamed a few of the utilities it produces, for example `shadow-sm` to `shadow-xs`, `rounded` to `rounded-sm` and `flex-grow` to `grow`. On Tailwind
29
+ v4, check the converted classes against the [renamed utilities](https://tailwindcss.com/docs/upgrade-guide#renamed-utilities) list of the Tailwind upgrade guide.
30
+
31
+ A handful of PrimeFlex classes have no Tailwind counterpart and are left alone. Replace them with flexbox or grid utilities by hand:
32
+
33
+ - formgrid
34
+ - formgroup
35
+ - formgroup-inline
36
+ - col
37
+ - col-fixed
38
+ - field
39
+ - field-checkbox
40
+ - field-radiobutton
41
+ - reset
12
42
 
13
43
  ## Overview
14
44
 
15
- PrimeFlex was PrimeTek's lightweight CSS utility library, designed to accompany PrimeNG. PrimeTek stopped maintaining it before the relicensing, on the grounds that most applications already bring their own utility layer — Tailwind, Bootstrap or something in-house — and a second one only overlaps with it. ExhaustiveUI does not maintain PrimeFlex either, and for the same reason. Nothing in this library depends on it, and no component requires it. If your application already uses PrimeFlex it will keep working, but it will not receive updates from us, and we suggest moving to Tailwind CSS.
45
+ [PrimeFlex](https://primeflex.org) was PrimeTek's lightweight CSS utility library, designed to accompany PrimeNG. PrimeTek stopped maintaining it before the relicensing, on the
46
+ grounds that most applications already bring their own utility layer — Tailwind, Bootstrap or something in-house — and a second one only overlaps with it.
47
+
48
+ ExhaustiveUI does not maintain PrimeFlex either, and for the same reason. Nothing in this library depends on it, and no component requires it. If your application already uses PrimeFlex it will keep working, but it will not receive
49
+ updates from us, and we suggest moving to Tailwind CSS.
16
50
 
17
51
  ## Tailwindcss
18
52
 
19
- Tailwind CSS is the replacement we suggest. This documentation site is itself built with it, and we publish @exhaustive-ui/tailwindcss for first-class integration — a plugin that teaches Tailwind about the theme's design tokens and puts the component styles in a cascade layer you can override cleanly. See the Tailwind CSS guide for setup with either Tailwind v3 or v4, and the next section for converting existing PrimeFlex classes.
53
+ Tailwind CSS is the replacement we suggest. This documentation site is itself built with it, and we publish `@exhaustive-ui/tailwindcss` for first-class integration — a plugin that teaches Tailwind about the theme's design
54
+ tokens and puts the component styles in a cascade layer you can override cleanly.
55
+
56
+ See the [Tailwind CSS guide](https://exhaustive-ui.com/tailwind) for setup with either Tailwind v3 or v4, and the next section for converting existing PrimeFlex classes.
20
57
 
package/data/pages/rtl.md CHANGED
@@ -4,7 +4,10 @@ Right-to-left support for ExhaustiveUI components.
4
4
 
5
5
  ## Configuration
6
6
 
7
- The ExhaustiveUI components natively support Right-to-Left (RTL) text direction through a modern CSS implementation utilizing FlexBox and classes like *-inline-start and *-block-end . Consequently, no JavaScript configuration is necessary; setting the document's text direction to RTL is sufficient to enable this feature. The RTL setting can either be set using the dir attribute or with the direction style property.
7
+ The ExhaustiveUI components natively support Right-to-Left (RTL) text direction through a modern CSS implementation utilizing FlexBox and classes like `*-inline-start` and `*-block-end`. Consequently, no JavaScript
8
+ configuration is necessary; setting the document's text direction to RTL is sufficient to enable this feature.
9
+
10
+ The RTL setting can either be set using the `dir` attribute or with the `direction` style property.
8
11
 
9
12
  ## Limitations
10
13