{"id":582,"date":"2017-01-25T00:00:00","date_gmt":"2017-01-25T08:00:00","guid":{"rendered":"http:\/\/officedevblogs.wpengine.com\/?p=582"},"modified":"2021-11-15T11:27:30","modified_gmt":"2021-11-15T19:27:30","slug":"sharepoint-pnp-javascript-core-library-v20","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/microsoft365dev\/sharepoint-pnp-javascript-core-library-v20\/","title":{"rendered":"SharePoint PnP JavaScript Core Library v2.0"},"content":{"rendered":"
\n

\"Banner<\/p>\n

The SharePoint Patterns and Practices JavaScript Core Library<\/a> was created to help developers by simplifying common operations within SharePoint and the SharePoint Framework. This is open source, community driven library with contributions cross different organizations and teams. 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. PnP JS Core library can be used in SharePoint Online or in on-premises. It’s a great library to be used with SharePoint Framework customizations<\/a>, but it can be also used using classic development models, like with Script Editor Web Part or when you embed JavaScript to SharePoint using User Custom Actions.<\/p>\n

The latest release, 2.0.0, of the Patterns and Practices JavaScript Core Library<\/a> represents an exciting milestone in library evolution and is thanks to all of the great contributions, feedback, and ideas from the community. Thank you all! <\/p>\n

\"Git<\/p>\n

Reorganization<\/h2>\n

If you are a contributor to the library, one of the first things you’ve likely noticed in the dev branch is that we moved things around. We added a debug folder (more on that below) and removed provisioning code. The provisioning code can now be found in a new repository<\/a> where it can grow and evolve on its own. We also reorganized and simplified the gulp tasks<\/a> – though all of the expected functionality remains in place.<\/p>\n

Debugging<\/h2>\n

Taking into account feedback and a desire to enhance the development experience we added support for debugging directly in the library. This will help with folks developing new features or fixing bugs as you can directly test, set break points, and step through the internals of the library. The full steps are outlined here<\/a>.<\/p>\n

Wiki Enhancements<\/h2>\n

Another piece of feedback we heard is a need for better documentation and we have started to enhance the wiki<\/a> to include deeper details around configuring, using, and extending the library. We have reorganized the menu to help guide you to the information you need to be successful. As always these articles are a work in progress and the community is encouraged to help us create new articles or update existing ones.<\/p>\n

Enhancements<\/h2>\n