Upgrade to PrimeNG 18

Proprietary

Migrates PrimeNG 17.x applications to PrimeNG 18. Renames components, migrates PrimeNGConfig to PrimeNG (with signal-backed setters), comments out the obsolete primeng/resources style entries in angular.json, wires providePrimeNG({ theme: { preset: Aura } }) into the root NgModule and adds @primeng/themes to package.json. Anything that can't be deterministically migrated (removed-and-no-direct-replacement components, deprecated CSS classes, structural template changes) gets a TODO comment in source plus a row in the ManualMigrationSteps data table for an agent or human to finish.

org.openrewrite.primeng.UpgradeTo18
mod run . --recipe=org.openrewrite.primeng.UpgradeTo18

Install it once, then run it on every repository under the current directory. New to the Moderne CLI? Set it up.

Recipe list

It runs these recipes, in this order.

  1. Upgrade to Angular 18
  2. Upgrade PrimeNG components to 18
  3. Migrate PrimeNGConfig to PrimeNG
  4. Migrate PrimeNG config field assignments to .set()
  5. Add providePrimeNG with a detected theme preset to the root NgModule
  6. org.openrewrite.javascript.AddDependency
  7. org.openrewrite.javascript.UpgradeDependencyVersion