SharePoint Framework v1.7.1 release notes

This release is primarily a bug fix release to address few regressions and missed bugs that were introduced in the 1.7 release. This didn't contain any critical issues, we rather wanted to fix few inconveniences with the latest release.

Released: December 18, 2018

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.7 to v1.7.1

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

1. Uninstall the existing v1.7 package:

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

2. Install the refreshed v1.7.1 package:

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

Warning

Upgrading from a previous minor version requires changes across package versions, build configuration files, and toolchain settings that vary depending on your source version. Manually updating package.json alone will result in build failures.

Tip

To upgrade this project, run:

npx -p @pnp/cli-microsoft365 m365 spfx project upgrade --toVersion 1.7.1 --output md

This analyzes your project and outputs all required changes, including a single script to apply them in one go.

Note

The CLI for Microsoft 365 is an open-source solution with active community providing support for it. There is no SLA for the open-source tool support from Microsoft.

Changes in this release

• Update title of user data property title in dynamic data
• Add workaround for Yarn's @types/react resolution issue
• Don't show/provision beta components in the non-beta install.
• Update debugger launch.json config.
• Add a dependency on TypeScript to meet the peer dependency requirements of tslint-microsoft-contrib.