Skip to content

Latest commit

 

History

History
54 lines (37 loc) · 2.48 KB

release-1.17.2.md

File metadata and controls

54 lines (37 loc) · 2.48 KB
title description ms.date ms.localizationpriority
SharePoint Framework v1.17.2 release notes
Release notes for the SharePoint Framework v1.17.2 release
05/09/2023
high

SharePoint Framework v1.17.2 release notes

This is a minor bump that fixes the issues around SharePoint Framework solution packaging, provides improved default scaffolding and few other minor adjustments, which were in the previous released 1.17 version and 1.17.1 version.

We are looking into release more frequent smaller release to be available also in future to address new findings or to address any other known issues which have been fixed.

Tip

It's safe to keep on using SharePoint Framework 1.17 version, but we do recommend using always the latest version in the production, which in this case would be the 1.17.2, which has few minor improvements as listed below.

Released: May 8, 2023

[!INCLUDE spfx-release-notes-common]

Install the latest version

Install the latest release of the SharePoint Framework (SPFx) by including the @latest tag:

npm install @microsoft/generator-sharepoint@latest --global

Upgrading projects from v1.17 to v1.17.2

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

    1. Uninstall the existing v1.17 package:

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

    2. Install the new v1.17.2 package:

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

[!INCLUDE spfx-release-upgrade-tip]

Fixed Issues

Here's a list of specific issues fixed around SharePoint Framework since the previous public release.

  • #8939 - Error can't find stylesheet to import
  • #8945 - New scaffolded projects contain phantom dependencies and do not compile with pnpm
  • #8887 - SPFx 1.17 - Conflicting package dependencies
  • #8936 - Default debugging type of 'edge' creates error
  • #8930 - SPFx error during gulp serve
  • SPFX_SERVE_TENANT_DOMAIN warning should not be shown for gulp serve --nobrowser