Office Development MVP / Office 365 & Azure Development

 

Version 1.13.0 of the SharePoint Framework React Controls (@pnp/spfx-controls-react) has been released. This is an open source library that shares a set of reusable React controls, which can be used in your SharePoint Framework solutions. This release includes the following changes: New control(s) Progress: New control added #230 DateTimePicker: New control added #21 RichText: New control added #20 Enhancements

 

Since the release of SharePoint Framework 1.8.0, you will gain control over which TypeScript version to run in the build process. Until the release of 1.8.0 version, we were always tight to TypeScript version 2.4.2. There was no way to change this, as it was part of the internal SPFx build engine, but this has changed.

 

A new version of SharePoint Framework was just released and one of the great things is that some of the dependencies were bumped. In version SPFx version 1.8.0, TypeScript was updated to 2.7.2 and React to 16.7.0. The React version is not even so old; it was released in December 2018 and comes with some handy features like lazy loading of components.

 

When developing solutions with SharePoint Framework it can happen that you need to navigate to another page from code. Normally in JavaScript or TypeScript this is very easy. All you have to do is set the new location like this: location.href = "<your-url>"; When you do this in SharePoint Framework, it has the side effect that it fully reloads the page you are navigating to.

 

Version 1.12.0 of the SharePoint Framework React Controls (@pnp/spfx-controls-react) has been released. This is an open source library that shares a set of reusable React controls, which can be used in your SharePoint Framework solutions. This release includes the following changes: New control(s) ListItemAttachments: New control added #177 IFramePanel: New control added #226 Enhancements

 

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: