Feature Request: Add PrimeNG as an Official or Optional UI Library for ABP Angular

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

No response

Describe the solution you'd like

Feature Request: Add PrimeNG as an Official or Optional UI Library for ABP Angular

Summary

It would be great if ABP Angular could officially support PrimeNG as an additional UI library option, either as an alternative to the current default UI stack or as an optional integration.

PrimeNG is actively maintained, modern, and usually provides stable releases aligned with new Angular versions. This makes it a strong candidate for ABP-based Angular applications that want to stay up to date with the Angular ecosystem.

Motivation

Currently, ABP Angular is strongly tied to its existing UI approach. However, many Angular projects are moving toward more modern UI stacks such as PrimeNG and Tailwind CSS, instead of older Bootstrap-based solutions such as ng-bootstrap.

PrimeNG offers:

• Regular compatibility updates for new Angular releases
• A modern and comprehensive component library
• Good enterprise application support
• A large set of ready-to-use UI components
• Strong theming capabilities
• Better alignment with modern Angular development
• Optional integration with Tailwind CSS or utility-first styling approaches

Adding PrimeNG support would make ABP Angular more flexible and attractive for developers who prefer a modern Angular UI ecosystem.

Proposed Solution

ABP could provide PrimeNG support in one of the following ways:

1. Add PrimeNG as an official alternative UI package for Angular.

2. Provide a PrimeNG-based theme or starter template.

3. Offer PrimeNG schematics or documentation for replacing the default UI components.

4. Allow developers to choose between the current UI stack and PrimeNG during project creation.

5. Provide PrimeNG-compatible implementations for common ABP UI elements such as:

   • Layout
   • Menus
   • Tables
   • Forms
   • Modals
   • Toasts / notifications
   • Permission-based UI elements
   • Localization-aware components

Benefits

This would provide several benefits for ABP users:

• Better support for modern Angular UI development
• Easier upgrades when new Angular versions are released
• More flexibility for teams with existing PrimeNG experience
• Improved developer experience
• More modern UI options out of the box
• Reduced dependency on Bootstrap-based UI libraries
• Better alignment with enterprise Angular projects

Additional Context

PrimeNG has become one of the most popular UI libraries in the Angular ecosystem. Since it regularly releases stable versions compatible with new Angular releases, it could help ABP Angular projects stay modern and easier to maintain over time.

This does not necessarily need to replace the current UI stack. It could also be introduced as an additional supported option, allowing teams to choose the UI library that best fits their project.

Additional context

No response

No files, tests, or entry points are named. Start by reviewing the existing ABP Angular UI stack and project-creation options, then determine which of the proposed scopes—official package, theme, starter template, schematics, documentation, or component implementations—would be supported and how completion would be verified.