PnP JSCore 3.0.0 (sp-pnp-js@3.0.0)
This month’s release of sp-pnp-js, 3.0.0, marks a big step - this will be the last major release for sp-pnp-js, details below - more and better is coming. Please give it a try and let us know if you see any issues. Be sure to check out the developer guide and happy coding!
When moving to this release we recommend reviewing the guide as there has been some restructuring of the library. The core use cases should remain relatively unchanged, but expect to make some changes when moving.
New Features
- Graph Support! - Currently with some limitations. Docs and examples coming. Official MS Graph docs
- Support for the RenderListDataAsStream method [PR] [Issue]
- Performance improvement for updating list items [PR] [Issue] [Example]
- Added section on updating file properties after upload
- Guide for moving from 2 .0.* to 3.0.*
Fixes & Updates
- Chaining .getByLoginName(login).groups loses LoginName parameter [Issue] [PR]
- Files API does not work from within add-in webs [Issue] [PR]
What is next for sp-pnp-js?
As I mentioned at the top of the post 3.0.0 will be the final major release for sp-pnp-js. We will continue to patch this release for critical bugs or blocking issues, however new features will no longer be added. Instead we are moving development to a new repo and releasing scoped packages under @pnp. This is a big change, and we understand a disruptive one. But ultimately it is the right thing to do for a number of reasons:
- Greater freedom to publish individual packages within the scope
- Allows us to expand our coverage beyond SharePoint, without forcing folks to take one huge package
- Gives greater flexibility to folks consuming the library to choose the pieces they want to use and extend
- Makes the pnp library align with how others large projects are managed (mono-repo, lock-step versioning, scopes, es2015 modules included in package)
There are beta versions of the new libraries published. These are a preview and to provide a way to see where we are heading and get constructive feedback. We do not yet suggest using these in any production code, continue to use the 2.0.* or 3.0.* versions of sp-pnp-js. If you don't need any of the new functionality or bug fixes in 3.0.0, we recommend staying within the 2.0.* stream and then make your upgrade effort to @pnp/*.
For any issues you find in sp-pnp-js please continue to report them to the same issues list, and we will be patching bugs so folks aren't stuck.
Once we are ready to begin transitioning to the new libraries we'll ensure we have a transition guide, docs, and samples to make things as easy as possible.
Thank You
I wanted to add a big thank you to everyone that uses, supports, and provides feedback on the library. You have made this a success and enabled us to grow to this point. I am excited for what is to come and sharing the journey with you all. And give the new repo a look and a star. Thank you.
What is the JS Core Component?
The Patterns and Practices JavaScript Core Library was created to help developers by simplifying common operations within SharePoint and the SharePoint Framework. Currently it contains a fluent API for working with the full SharePoint REST API as well as utility and helper functions. This takes the guess work out of creating REST requests, letting developers focus on the what and less on the how.
“Sharing is Caring”