Something that is giving me some trouble for a long time is that the SharePoint Framework build process treads warnings as errors in production builds (when the **--ship** flag is present). Let's start by giving some background information. During bundling/packaging of your SharePoint Framework solution, you could see two types of messages: * Warnings * Errors {{}} When running a DEBUG
Version 1.14.1 of the SharePoint Framework Property Controls (`@pnp/spfx-property-controls`) has been released. This is an open source library that shares a set of reusable property pane controls, which can be used in your SharePoint Framework solutions. This release includes the following changes: **Fixes** * `TaxonomyPicker`: Terms are sorted incorrectly under the wrong parent [#153](https://github.com/SharePoint/sp-dev-fx-property-controls/issues/153) * `EnterpriseTermPicker`: Terms are sorted incorrectly
When building custom gulp tasks in your SharePoint Framework solutions, it might be handy to log as the default build system does. > More information about building custom gulp tasks can be found here: [Integrate gulp tasks in SharePoint Framework toolchain](https://docs.microsoft.com/en-us/sharepoint/dev/spfx/toolchain/integrate-gulp-tasks-in-build-pipeline "Integrate gulp tasks in SharePoint Framework toolchain") When you would use the default **console.log**, **console.warn**,** **or **console.error** methods like this: {{}} They will just
If you are working on a SharePoint Framework solution which has to support multiple languages. You will already know that the localized labels are created in localization (resource) files which are "just" JavaScript files. There is actually nothing wrong with this approach in SharePoint Framework, although you could experience some issues with it. > **Info**: More information about localizing web part
Azure Functions are a great and easy way for implementing and automating tasks for your SharePoint Online environment. You could use it for various tasks like implementing scheduled jobs (timer jobs), elevating permissions via an API call to fetch/create data, ... Starting to create new Azure Functions is simple with the Azure Functions project template in Visual Studio. {{}} But there is an
Version 1.14.0 of the SharePoint Framework Property Controls (`@pnp/spfx-property-controls`) has been released. This is an open source library that shares a set of reusable property pane controls, which can be used in your SharePoint Framework solutions. This release includes the following changes: **New control(s)** * `PropertyFieldEnterpriseTermPicker`: New control to load term sets by using `@pnp/pnpjs` [#70](https://github.com/SharePoint/sp-dev-fx-property-controls/issues/70) [#120](https://github.com/SharePoint/sp-dev-fx-property-controls/issues/120) **Enhancements** * `PropertyFieldCollectionData`: Setting
Let's build together
Manage content in VS Code
Present from VS Code
Engage with your audience throughout the event lifecycle
