Animation of the library in use, note intellisense help in building your queries
These articles provide general guidance for working with the libraries. If you are migrating from sp-pnp-js please review the transition guide.
- Getting Started
- Getting Started Contributing
- Gulp Commands
- Install Beta Versions
- Package Structure
Patterns and Practices client side libraries (PnPjs) are comprised of the packages listed below. All of the packages are published as a set and depend on their peers within the @pnp scope.
|common||Provides shared functionality across all pnp libraries|
|config-store||Provides a way to manage configuration within your application|
|graph||Provides a fluent api for working with Microsoft Graph|
|logging||Light-weight, subscribable logging framework|
|nodejs||Provides functionality enabling the @pnp libraries within nodejs|
|odata||Provides shared odata functionality and base classes|
|pnpjs||Rollup library of core functionality (mimics sp-pnp-js)|
|sp||Provides a fluent api for working with SharePoint REST|
|sp-addinhelpers||Provides functionality for working within SharePoint add-ins|
|sp-clientsvc||Provides based classes used to create a fluent api for working with SharePoint Managed Metadata|
|sp-taxonomy||Provides a fluent api for working with SharePoint Managed Metadata|
Issues, Questions, Ideas¶
Please log an issue using our template as a guide. This will let us track your request and ensure we respond. We appreciate any contructive feedback, questions, ideas, or bug reports with our thanks for giving back to the project.
Code of Conduct¶
"Sharing is Caring"¶
Please use http://aka.ms/sppnp for the latest updates around the whole SharePoint Patterns and Practices (PnP) program.
THIS CODE IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING ANY IMPLIED WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR NON-INFRINGEMENT.