primefaces / primefaces/primereact-examples
Migration Tool / Codemod for v10 → v11
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 142
- Forks
- 107
- PR merge metrics
- No merged PRs in 30d
Description
First of all, congratulations on the v11 release. The new compound component architecture looks modern and flexible.
However, migrating from v10 to v11 appears to require significant manual work. For medium to large applications using components such as DataTable, Dialog, Dropdown, TreeTable, and others, the migration effort can be substantial.
Since many APIs have changed from the previous declarative style to the new compound component approach, it would be extremely helpful to have an official migration tool (codemod) that can automate the common transformations.
For example, a tool such as:
npx @primereact/codemod v11
could:
- Update imports.
- Transform common component patterns where possible.
- Flag cases that require manual intervention.
- Generate TODO comments for unsupported scenarios.
Even if the migration cannot be fully automated, handling 70–80% of the repetitive changes would save developers a significant amount of time and reduce migration errors.
Are there any plans to provide an official migration utility or codemod for upgrading existing v10 applications to v11?
Thank you for your work on PrimeReact.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No files, tests, or entry points are named. Start by inventorying the v10-to-v11 API changes for DataTable, Dialog, Dropdown, TreeTable, and other components, then define which common transformations the codemod can support. Done means an official utility updates imports and supported patterns while flagging manual cases and generating TODO comments for unsupported scenarios.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100