Not
Bu sayfaya erişim yetkilendirme gerektiriyor. Oturum açmayı veya dizinleri değiştirmeyi deneyebilirsiniz.
Bu sayfaya erişim yetkilendirme gerektiriyor. Dizinleri değiştirmeyi deneyebilirsiniz.
This is mainly a bug fix release to address few regressions, which were introduced in the v1.5 release.
Released: June 26, 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.5 to v1.5.1
In the project's package.json file, identify all SPFx v1.5 packages. For each SPFx package:
Uninstall the existing v1.5 package:
npm uninstall @microsoft/{spfx-package-name}@1.5Install the refreshed v1.5.1 package:
npm install @microsoft/{spfx-package-name}@1.5.1 --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.5.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
- Fixed the issue in the yeoman generator that blocked you from creating different types of components in your package.
- Changed the visibility of some SPFx APIs to move them to Beta (and will now appear in the typings when you use the --plusbeta versions of the packages. The APIs added to the --plusbeta packages are: