Skip to content

Commit bfd0950

Browse files
revert guidance to focus on spfx v1.11 (SharePoint#6872)
- revert changes to "set up dev env for spfx" to focus on SPFx v1.11 - fixes SharePoint#6868
1 parent d5b8768 commit bfd0950

File tree

3 files changed

+10
-70
lines changed

3 files changed

+10
-70
lines changed

docs/spfx/release-1.12.0.md

Lines changed: 7 additions & 58 deletions
Original file line numberDiff line numberDiff line change
@@ -1,68 +1,17 @@
11
---
2-
title: SharePoint Framework v1.12 release notes
3-
description: Release notes for the SharePoint Framework v1.12 release
4-
ms.date: 03/17/2021
2+
title: SharePoint Framework v1.12.0 release notes
3+
description: Release notes for the SharePoint Framework v1.12.0 release
4+
ms.date: 03/30/2021
55
ms.prod: sharepoint
66
localization_priority: Priority
77
---
8-
# SharePoint Framework v1.12 release notes
8+
# SharePoint Framework v1.12.0 release notes
99

1010
This release introduces a new property & event in the Web Part API to detect the rendering width (and changes), improved support for Microsoft Teams solutions, and updates supported versions of Node.js.
1111

1212
**Released:** March 15, 2021
1313

14-
1514
> [!CAUTION]
16-
> Version 1.12 release is currently considered as deprecated due the unexpected regressions. We recommend usage of [v1.11](release-1.11.0.md) until updated version is available.
17-
18-
## Upgrading projects from v1.11 to v1.12
19-
20-
1. In the project's **package.json** file, identify all SPFx v1.11 packages. For each SPFx package:
21-
1. Uninstall the existing v1.11 package:
22-
23-
```console
24-
npm uninstall @microsoft/{spfx-package-name}@1.11
25-
```
26-
27-
1. Install the refreshed v1.12 {version-release} package:
28-
29-
```console
30-
npm install @microsoft/{spfx-package-name}@1.12 --save --save-exact
31-
```
32-
33-
> [!TIP]
34-
> The [CLI for Microsoft 365](https://aka.ms/o365cli) provides an easy step-by-step guidance to [upgrade](https://pnp.github.io/cli-microsoft365/cmd/spfx/project/project-upgrade/) your solutions to latest SharePoint Framework version.
35-
36-
[!INCLUDE [pnp-o365cli](../../includes/snippets/open-source/pnp-o365cli.md)]
37-
38-
## New features and capabilities
39-
40-
- The **Sync to Teams** button in the Tenant App Catalog will use the Teams app manifest defined in the solution if present to create and publish a Teams app package to Microsoft Teams. If an app manifest file is not present, SharePoint will dynamically generate one.
41-
- *See [Deployment options for SharePoint Framework solutions for Microsoft Teams](deployment-spfx-teams-solutions.md) for more details.*
42-
- A new API has been added to the SPFx web part class to determine the rendered width of a web part and optionally handle an event when it changes.
43-
- *See [Determine the rendered web part size](web-parts/basics/determine-web-part-width.md) for more details.*
44-
- Preliminary support for Microsoft Teams meeting apps with the SharePoint Framework - full support is pending a fix for server side regression
45-
46-
## Changes in this release
47-
48-
- Add support for **Node.js v12**
49-
- *See [Set up your SharePoint Framework development environment](set-up-your-development-environment.md) for details.*
50-
- **Gulp v4** (installed globally) is required (*see [Regarding Gulp versions & Node.js v12+](#gulp-versions--nodejs-v12) for details*)
51-
- For all projects:
52-
- Update the default version of TypeScript to **v3.7** (*via **@microsoft/rush-stack-compiler-3.7** v0.2.3*)
53-
- Update the **Gulp** version used to **v4.0.2**
54-
- For projects that use React:
55-
- Update the React NPM packages (**react** & **react-dom**) to **v16.9.0**.
56-
- Update the Office UI Fabric React NPM package / Microsoft Fluent UI (**office-ui-fabric-react**) to **v7.156.0**.
57-
58-
## Deprecations and removed items in this release
59-
60-
- **Gulp v3** is not supported (*neither globally nor locally installed*) when using Node.js v12+.
61-
- **Local workbench is deprecated** - This is the last release that will include support for the local workbench.
62-
- This is the last release that will include a single generator that works for on-prem and SharePoint Online. You'll still be able to create projects for on-prem, just by using the older generator.
63-
64-
### Gulp versions & Node.js v12+
65-
66-
Gulp v3 isn't supported with Node.js v12+ (*ref [gulpjs/gulp/#2324](https://github.com/gulpjs/gulp/issues/2324)*).
67-
68-
This is not a change with SPFx. Its mentioned here to bring attention to it as this SPFx release adds support for Node.js v12.
15+
> Version 1.12 release is currently considered as deprecated and has been unpublished due the unexpected regressions.
16+
>
17+
> We recommend usage of [v1.11](release-1.11.0.md) until updated version is available.

docs/spfx/set-up-your-development-environment.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Set up your SharePoint Framework development environment
33
description: Use Visual Studio or your own custom development environment to build SharePoint Framework solutions. You can use macOS, Windows, or Linux.
4-
ms.date: 03/15/2021
4+
ms.date: 03/30/2021
55
ms.prod: sharepoint
66
localization_priority: Priority
77
ms.custom: scenarios:getting-started
@@ -19,7 +19,7 @@ You can also follow these steps by watching this video on the SharePoint PnP You
1919
2020
## Install Node.js
2121

22-
Install the latest version of **[Node.js](https://www.nodejs.org) LTS v12.x**.
22+
Install the latest version of **[Node.js](https://www.nodejs.org) LTS v10.x**.
2323

2424
This version is the currently recommended version of Node.js to use with the SharePoint Framework (*unless otherwise specified below*).
2525

@@ -41,10 +41,9 @@ You can check if you already have Node.js already installed, including installed
4141
node -v
4242
```
4343

44-
The SharePoint Framework v1.12 is supported on the following Node.js versions:
44+
The SharePoint Framework v1.11 is supported on the following Node.js versions:
4545

4646
- Node.js v10 (*Dubnium*)
47-
- Node.js v12 (*Erbium*)
4847

4948
> [!CAUTION]
5049
> If you're building SharePoint Framework components for SharePoint Server 2016, see **[SPFx & SharePoint Server 2016](#spfx--sharepoint-server-2016)** section for additional details on which version of Node.js you should install.
@@ -80,12 +79,6 @@ Enter the following command to install Gulp:
8079
npm install gulp --global
8180
```
8281
83-
> [!NOTE]
84-
> Gulp v3 was used as the target for all Gulp tasks in the SPFx build toolchain prior to SPFx v1.12. If you are using Node.js v12+, you must install Gulp v4 globally because Gulp v3 is not supported on Node.js v12+.
85-
>
86-
> - Refer to [Check the version of globally installed packages](#check-the-version-of-globally-installed-packages) to find the version you currently have installed.
87-
> - Refer to the [SharePoint Framework v1.12 release notes](release-1.12.0.md) for additional details.
88-
8982
### Install Yeoman
9083

9184
[Yeoman](https://yeoman.io/) helps you kick-start new projects, and prescribes best practices and tools to help you stay productive. SharePoint client-side development tools include a Yeoman generator for creating new web parts. The generator provides common build tools, common boilerplate code, and a common playground website to host web parts for testing.

docs/toc.yml

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -426,8 +426,6 @@
426426
items:
427427
- name: Overview
428428
href: spfx/roadmap.md
429-
- name: SPFx v1.12.0 - March 17, 2021
430-
href: spfx/release-1.12.0.md
431429
- name: SPFx v1.11.0 - July 16, 2020
432430
href: spfx/release-1.11.0.md
433431
- name: SPFx v1.10.0 - January 7, 2020

0 commit comments

Comments
 (0)