Edit

Share via

SharePoint Framework v1.9.1 release notes

  • Article

This is a minor release that includes Library component moving to general availability and the tooling move from WebPack 3 to WebPack 4. There are some minor changes in support for the Teams SDK as well.

Released: August 14, 2019

Important

This page addresses details related to a specific SPFx release version. This page doesn't include additional SPFx prerequisites that must be installed in order to develop SPFx solutions, including Node.js, Yeoman, and other tools.

To learn more about these prerequisites, see Set up your SharePoint Framework development environment.

Upgrading projects from v1.8.2 to v1.9.1

In the project's package.json file, identify all SPFx v1.8.2 packages. For each SPFx package:

  1. Uninstall the existing v1.8.2 package:

    npm uninstall @microsoft/{spfx-package-name}@1.8.2

  2. Install the refreshed v1.9.1 package:

    npm install @microsoft/{spfx-package-name}@1.9.1.0 --save --save-exact

Tip

The CLI for Microsoft 365 provides an easy step-by-step guidance to upgrade your solutions to latest SharePoint Framework version.

New features and capabilities

Changes in this release

  • Upgraded SPFx tooling from Webpack to Webpack 4. You won't notice an impact with this change in how you use the tooling, and many webpack plugins should work. However, if you modified the webpack step, you may need to update your changes to webpack 4.

  • Microsoft Teams SDK updated to v1.4.2. This version has support for Vanity URLs.

  • We've added an sdks property on the web part context API where we'll start to host specific application SDKs. Microsoft Teams is the first one to use this new API.

    We've marked the previous context.microsoftTeams API as deprecated (but it will continue to work).

  • We continue to improve the admin experience around approving API requests in the service.

Deprecations and removed items in this release

  • Removed the previously deprecated GraphHttpClient API from the SPFx API. Code using it will still work for the short term, but you should migrate your code to the MSGraphClient API.
  • The microsoftTeams API on a component's context object has been deprecated in favor of the new context.sdk.microsoftTeams API as mentioned above.

Note

What happened to the SPFx v1.9.0 release?

There was an issue with the local workbench in the v1.9.0 release, so it was pulled and now replaced with 1.9.1 release. Issue was not critical, but as it caused confusion, we wanted to ensure that usage is smooth without any additional hacks or other adjustments.