primefaces / primefaces/primereact
Dependency conflict between jspdf v4 and jspdf-autotable during npm install
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 8.3k
- Forks
- 1.2k
- PR merge metrics
- No merged PRs in 30d
Description
Bug Description
There is a dependency conflict when installing the PrimeReact repository locally.
Current behavior:
After cloning the repository and running:
npm install
npm fails with a dependency resolution error related to jspdf and jspdf-autotable.
Error:
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: primereact@10.9.8
npm error Found: jspdf@4.0.0
npm error node_modules/jspdf
npm error jspdf@"4.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer jspdf@"^2 || ^3" from jspdf-autotable@5.0.2
npm error node_modules/jspdf-autotable
npm error jspdf-autotable@"5.0.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken)
npm error dependency resolution.
npm error
npm error For a full report see:
npm error /home/loki/.npm/_logs/2026-05-18T13_07_46_040Z-eresolve-report.txt
npm error A complete log of this run can be found in:
npm error /home/loki/.npm/_logs/2026-05-18T13_07_46_040Z-debug-0.log
Expected behavior:
The repository should install successfully with:
npm install
without requiring --force or --legacy-peer-deps.
Environment:
- PrimeReact: 10.9.8
- jspdf: 4.x
- npm: 10.9.2
- Node.js: v23.7.0
Steps to reproduce:
- Clone the PrimeReact repository
- Navigate to the project directory
- Run:
npm install
- Observe dependency resolution failure
Suggested fix:
Update the jspdf-autotable dependency to a version compatible with jspdf v4.
Contributor guide
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
Start by reproducing the failure with npm install and inspecting the root dependency declarations for jspdf and jspdf-autotable. Check which jspdf-autotable release supports jspdf 4, update the dependency declaration, and verify that a clean npm install completes without force or legacy-peer-deps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100