|
| 1 | +--- |
| 2 | +title: SharePoint Framework v1.15 preview release notes |
| 3 | +description: Release notes for the SharePoint Framework v1.15 preview release |
| 4 | +ms.date: 3/3/2022 |
| 5 | +ms.prod: sharepoint |
| 6 | +ms.localizationpriority: high |
| 7 | +--- |
| 8 | +# SharePoint Framework v1.15 preview release notes |
| 9 | + |
| 10 | +There will be multiple public preview release using the @next tag in the NPMJS.org registry before final release candidates and a final public release. |
| 11 | + |
| 12 | +[!INCLUDE [spfx-release-beta](../../includes/snippets/spfx-release-beta.md)] |
| 13 | + |
| 14 | +**beta.1:** March 3, 2022 |
| 15 | + |
| 16 | +[!INCLUDE [spfx-release-notes-common](../../includes/snippets/spfx-release-notes-common.md)] |
| 17 | + |
| 18 | +## Install the latest preview release |
| 19 | + |
| 20 | +Install the latest preview release of the SharePoint Framework (SPFx) by including the **@next** tag: |
| 21 | + |
| 22 | +```console |
| 23 | +npm install @microsoft/generator-sharepoint@next --global |
| 24 | +``` |
| 25 | + |
| 26 | +## Upgrading projects from v1.14 to v1.15 |
| 27 | + |
| 28 | +1. In the project's **package.json** file, identify all SPFx v1.14 packages. For each SPFx package: |
| 29 | + 1. Uninstall the existing v1.14 package: |
| 30 | + |
| 31 | + ```console |
| 32 | + npm uninstall @microsoft/[email protected] |
| 33 | + ``` |
| 34 | + |
| 35 | + 2. Install the new v1.14 preview package: |
| 36 | + |
| 37 | + ```console |
| 38 | + npm install @microsoft/generator-sharepoint@next --save --save-exact |
| 39 | + ``` |
| 40 | + |
| 41 | +[!INCLUDE [spfx-release-upgrade-tip](../../includes/snippets/spfx-release-upgrade-tip.md)] |
| 42 | + |
| 43 | +## New features and capabilities |
| 44 | + |
| 45 | +### Microsoft Graph V3 Support |
| 46 | + |
| 47 | +`MSGraphClientFactory` allows a developer to select the version of the Microsoft Graph API to use. |
| 48 | + |
| 49 | +> [!NOTE] |
| 50 | +> Default behavior is to use v1 of the Microsoft Graph API for backward compatibility. |
| 51 | + |
| 52 | +```typescript |
| 53 | +this.context.msGraphClientFactory.getClient('3'); |
| 54 | +``` |
| 55 | + |
| 56 | +### Updated Command Set Extension Template |
| 57 | + |
| 58 | +The template was updated to use `listViewStateChanged` event instead of deprecated `onListViewUpdated` event. |
| 59 | + |
| 60 | +### Node 16 LTS |
| 61 | + |
| 62 | +- Node engines updated in package.json files to include Node 16 LTS `>=12.13.0 <13.0.0 || >=14.15.0 <15.0.0 || >=16.13.0 <17.0.0`. |
| 63 | + |
| 64 | +## Deprecations |
| 65 | + |
| 66 | +- Deprecated SPComponentLoader#getManifests due to runtime performance overhead. |
| 67 | + |
| 68 | +## Fixed Issues |
| 69 | + |
| 70 | +### February Timeframe |
| 71 | + |
| 72 | +- [#7680](https://github.com/SharePoint/sp-dev-docs/issues/7680) - Theme colors do not load (immediately) on SP listpage or site contents page |
| 73 | +- [#6403](https://github.com/SharePoint/sp-dev-docs/issues/6403) - DynamicData.tryGetValue() should not fail if disposed |
| 74 | +- [#5979](https://github.com/SharePoint/sp-dev-docs/issues/5979) - Problem popup when remove SPFx Teams Tab |
| 75 | +- [#7679](https://github.com/SharePoint/sp-dev-docs/issues/7679) - Field customizer doesn't load consistently when searching |
| 76 | +- [#7689](https://github.com/SharePoint/sp-dev-docs/issues/7689) - [SPFx-Heft-Plugins][SPFx 1.13.1] elementManifests path resolving differently on Windows and Linux when referencing external file path |
| 77 | +- [#7771](https://github.com/SharePoint/sp-dev-docs/issues/7771) - SPFx v1.14.0: Image Helper API, exception in btoa, string contains characters outside of the Latin1 range |
0 commit comments