SharePoint Framework v1.17.3 release notes

This release is a minor bump that fixes the issues around SharePoint Framework solution packaging as listed further down in this document.

We're 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.


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.3, which has few minor improvements as listed in this document.

Released: May 31, 2023


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.

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.3

  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.3 package:

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


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

Fixed Issues

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

  • @fluentui/react package is referenced both as dependecy and devDependency in the generated package.json file for React Web Part
  • #8966 - Web part missing,Vanishes 1.17/1.17.1/1.17.2
  • #8953 - Lint error occurred with "@typescript-eslint/no-extra-semi"