Get rid of PrimeNG dependency
Maintainers usually reply within 1 day
@fateeand is already working on this.
Since Jul 1, 2026.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 30/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- angular, typescript
- Domain
- frontend
Research direction
Start by checking the cps-ui-kit dependency declarations to find where PrimeNG is required and then inspect the listed areas—Datepicker, Autocomplete, Notifications, Dialog, Tree autocomplete, Tree select, Tree table, Table, Menu—for PrimeNG imports. Read those components/services/directives first to map current touchpoints, then follow the quick-fix vs long-term direction described in #687. A successful result is that PrimeNG references are removed/replaced in this set and cps-ui-kit can be updated toward Angular 22 without that dependency.
Written by the indexing model from the issue text.
Description
From major version v22 onward, PrimeNG is no longer open-source: https://primeui.dev/nextchapter
The latest version available under the MIT license is 21.1.9. We need to remove this dependency from the cps-ui-kit.
The approach should look like this:
- A quick fix to unblock the library update to Angular 22
We need to copy the PrimeNG code we use into our repo and remove the dependency. The MIT license allows this as long as we keep the copyright notices and license text. Tracked by #687 - A long-term approach to migrate all the components/services/directives we use so they work without PrimeNG code
PrimeNG is currently used, either as utils or base components, in:
- Datepicker
- Autocomplete
- Notifications
- Dialog
- Tree autocomplete
- Tree select
- Tree table
- Table
- Menu
- Dominant language
- TypeScript
- Stars
- 9
- Forks
- 7
- Avg merge
- 11h 59m
- Merged PRs (30d)
- 8
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from AbsaOSS/cps-shared-ui
-
enhancement library
Difficulty 1/5 Under an hour Newbie friendliness 85/100
AbsaOSS/cps-shared-ui#644 ·
Maintainers usually reply within 1 day
-
library new component
Difficulty 3/5 Half a day Newbie friendliness 55/100
AbsaOSS/cps-shared-ui#853 ·
Maintainers usually reply within 1 day
-
library new component
Difficulty 3/5 1-2 days Newbie friendliness 62/100
AbsaOSS/cps-shared-ui#792 ·
Maintainers usually reply within 1 day
-
library tech-debt
Difficulty 3/5 1-2 days Newbie friendliness 55/100
AbsaOSS/cps-shared-ui#692 ·
Maintainers usually reply within 1 day
-
library tech-debt
Difficulty 3/5 1-2 days Newbie friendliness 55/100
AbsaOSS/cps-shared-ui#691 ·
Maintainers usually reply within 1 day
All issues in AbsaOSS/cps-shared-ui
Similar issues
-
ui(ListToolbar): search takes the full row on a phone instead of sharing it with the result countOpen
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Maintainers usually reply within 1 day
-
priority:high
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
immich-app/immich#32426 ·
Maintainers usually reply within 1 day
-
documentation good first issue hacktoberfest help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
libredb/libredb-studio#1756 ·
Maintainers usually reply within 1 day