pnp / pnp/sp-dev-fx-controls-react
Upgrading @pnp/sp
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 433
- Forks
- 418
- Avg merge
- 5d 6m
- Merged PRs (30d)
- 19
Description
Category
[x] Enhancement
[ ] Bug
[ ] Question
Version
Please specify what version of the library you are using: [3.21.0]
Expected / Desired Behavior / Question
I get that we need to upgrade dependencies carefully, but it seems a bit mad to me that this project is still on @pnp/sp 2.5.0, when that library is v4+. It's not a -major- issue but just curious what's holding it back?
Observed Behavior
N/A
Steps to Reproduce
N/A
Thanks
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
The issue does not name any files, tests, or entry points. Review the project's current @pnp/sp 2.5.0 dependency and its usage, then determine whether upgrading is compatible; done means documenting the blocker or completing the upgrade with validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- react, typescript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100