I am migrating a large-scale Angular application that uses PrimeNG from Angular 17 to Angular 18.
Up to Angular 17, we were using a compatible PrimeNG version where the resources folder existed inside node_modules/primeng. We imported the Saga Blue theme (theme.css) and primeng.min.css directly in the angular.json styles array, and the application worked correctly.
After upgrading to Angular 18 and the corresponding PrimeNG version, I noticed that PrimeNG has removed the resources folder, including the prebuilt themes and the primeng.min.css file. As a result, all PrimeNG components in our application are now unstyled or broken.
I followed the PrimeNG “Getting Started” documentation for the new version, but I am unclear about the following:
Is the Saga Blue theme still supported in PrimeNG version 18 or later?
If so, how can it be applied using the new theming system?
If not, what is the recommended migration path for applications that previously relied on Saga Blue?
What is the correct way to achieve Saga Blue–like styling in PrimeNG ≥18 when migrating from older versions?