Contents
SPFx has a solution for this. There is online version of the workbench, which can be found via ` [SHAREPOINT_WEB_URL]/_layouts/15/workbench.aspx`.
Use with SharePoint Framework web parts. You may choose to use the @pnp/sp library when building your SharePoint Framework (SPFx) web parts. This library provides a fluent API to make building your REST queries intuitive and supports batching and caching.
How does the web part of SPFX work?
SPFx web part is generally agnostic to the future location of the web. Web URL can be get known in a runtime using ` this.context.pageContext.web`’s object properties: `absoluteUrl ` or ` serverRelativeUrl `. REST requests are usually built using this variables.
How to use the @ PNP / SP library?
Because the @pnp/sp library constructs REST requests, it needs to know the URL to send these requests. When operating within classic sites and pages, we can make use of the global _spPageContextInfo variable. Within SPFx, this is not available, or if it is, it may not be correct. So we need to rely on the context object supplied by the framework.
The key difference to SharePoint Framework (SPFx) Extensions is that your page elements won’t change if changes are made to the HTML/DOM structure in SharePoint Online. This article describes how to extend your Hello World extension to take advantage of page placeholders.
When dealing with SharePoint Framework (SPFx), a developer can choose local or remote runtime debug strategy. By default by running ` gulp serve `, the local workbench is started.
Can you test SharePoint framework extensions on modern pages?
When building SharePoint Framework solutions, you can test them on modern SharePoint pages. For building SharePoint Framework extensions, testing on modern pages is the only option, since at this moment the SharePoint Workbench doesn’t support loading extensions.