Written by

Chanakya Jayabalan




see all categories

Time to migrate to pnp/pnp from sp-pnp-js (PnP core library)

SharePoint Patterns and Practices (PnP) is an open source initiative to share documentation, guidance, samples and reusable component for the community. All the SharePoint developer documentation across on-premises and online are coordinated by PnP. The PnP Core team comprises of Microsoft people and external MVPs. You can access the Microsoft Tech Community site here at http://aka.ms/sppnp-community

SharePoint PnP community update

SharePoint PnP community has announced that updates to sp-pnp-js library will be stopped by July 2018. An alternate to this is  PnP/PnP library, which will split sp-pnp-js in to multiple individual modules & this library would continue to get updates from now. 

The sp-pnp-js or generally referred to as the SharePoint PnP core library was developed to help developers to code basic operations within SharePoint & SharePoint framework. This has various implementations to work with REST APIs and few utility functions. This simplifies the process of development by enabling developers to call predefined methods rather than working with REST calls. 

The idea behind this is to split the ever growing single js in to multiple individual packages enabling developers to include only required packages to their code and also a better control and release capabilities to the community. 

How does this affect your current implementations?

The sp-pnp-js library would be receiving updates till July 2018 and will stay on npm thereafter. You can use them in your current solutions. There will be no impact to your existing solutions. Alternatively, you can also migrate to the new package at pnp/pnp to leverage the full power of future updates in your custom solutions.

What you have to do about this update?

Though your current solutions can refer to the existing library and run without any issues, its suggested that for any future developments you are requested to refer to the new package at pnp/pnp to get most benefit of the library. 

We at hubfly have started our migrations to the new pnp/pnp library. Don’t be late, plan your migrations and new development to align with the PnP community strategy. 


Chanakya Jayabalan

Written by Chanakya Jayabalan

Chanakya holds an MS from BITS, Pilani has over a decade of experience in Microsoft digital platforms both on-premises & on cloud, helping customers in the journey to make their digital transformation possible. His work involves architecting enterprise scale digital platforms & integrations by making right technology choices & solutions.