You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/spfx/release-1.12.1.md
+4-3Lines changed: 4 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: SharePoint Framework v1.12.1 release notes
3
3
description: Release notes for the SharePoint Framework v1.12.1 release
4
-
ms.date: 09/08/2021
4
+
ms.date: 12/28/2021
5
5
ms.prod: sharepoint
6
6
ms.localizationpriority: high
7
7
---
@@ -43,10 +43,11 @@ This release introduces a new property & event in the Web Part API to detect the
43
43
44
44
- Add support for **Node.js v12.13.x & v14.15.x**
45
45
- *See [Set up your SharePoint Framework development environment](set-up-your-development-environment.md) for details.*
46
-
- **Gulp v4** (installed globally) is required (*see [Regarding Gulp versions & Node.js v12+](#gulp-versions--nodejs-v12) for details*)
46
+
- **Gulp-CLI** is strongly recommended. Our prior guidance was to install Gulp v3 or v4 globally, but the guidance from the Gulp team is to only install Gulp CLI globally. By using the Gulp CLI, you can have projects that use Gulp v3 and others that use Gulp v4.
47
47
- For all projects:
48
48
- Update the default version of TypeScript to **v3.7** (*via **@microsoft/rush-stack-compiler-3.7** v0.2.3*)
49
-
- Update the **Gulp** version used to **v4.0.2**
49
+
- Update **Gulp** version used to **v4.0.2**
50
+
> *see [Regarding Gulp versions & Node.js v12+](#gulp-versions--nodejs-v12) for details*
50
51
- For projects that use React:
51
52
- Update the React NPM packages (**react** & **react-dom**) to **v16.9.0**.
52
53
- Update the Office UI Fabric React NPM package / Microsoft Fluent UI (**office-ui-fabric-react**) to **v7.156.0**.
Copy file name to clipboardExpand all lines: docs/spfx/sharepoint-2016-support.md
+18-6Lines changed: 18 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: SharePoint Framework development with SharePoint 2016 Feature Pack 2
3
3
description: SharePoint Server 2016 Feature Pack 2 supports SharePoint Framework client-side web parts hosted in classic SharePoint pages.
4
-
ms.date: 06/22/2021
4
+
ms.date: 12/28/2021
5
5
ms.localizationpriority: high
6
6
---
7
7
# SharePoint Framework development with SharePoint Server 2016 Feature Pack 2
@@ -54,12 +54,24 @@ The dependencies for SPFx v1.1 frameworks, tools, and the associated versions do
54
54
55
55
For example, Gulp v3.* is only supported up to Node.js v10, while Gulp v4.* is supported from Node.js v12 and higher. Because SPFx v1.1 is only supported on Node.js v6 and Node.js v8, you need to ensure you have an older version of Node.js installed as well as an older version of Gulp & Yeoman.
56
56
57
-
If you're building SPFx v1.1 solutions, install the following specific versions of Gulp & Yeoman:
57
+
> [!NOTE]
58
+
> The Gulp team introduced a separate package, [gulp-cli](https://www.npmjs.com/package/gulp-cli), that should be installed globally. It can be used by projects that use either Gulp v3 & Gulp v4.
59
+
>
60
+
> Learn more about the gulp-cli here: [gulpjs/gulp/#2324](https://github.com/gulpjs/gulp/issues/2324).
Microsoft recommends using the most recent version of the Yeoman generator for the SharePoint Framework ([@microsoft/generator-sharepoint](https://www.npmjs.com/package/@microsoft/generator-sharepoint)) that supports creating on-premises projects: SPFx v1.6.0.
63
+
64
+
> [!IMPORTANT]
65
+
> The Yeoman generator for the SharePoint Framework, starting with v1.13.0, only supports projects for SharePoint Online. Learn more about this change in the [SharePoint Framework v1.13 release notes](release-1.13.md). However, SPFx 1.1.1 only supports up to Node.js v6. Therefore, you need to get the latest version of the Yeoman generator for the SharePoint Framework (v1.6.0) that works on the same version of Node.js (v6) that SPFx v1.1.0 is supported on.
Copy file name to clipboardExpand all lines: docs/spfx/sharepoint-2019-support.md
+24-9Lines changed: 24 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -1,13 +1,16 @@
1
1
---
2
-
title: SharePoint Framework development with SharePoint 2019
2
+
title: SharePoint Framework development with SharePoint Server 2019 & SharePoint Server SE
3
3
description: SharePoint Server 2019 supports SharePoint Framework client-side web parts in classic and modern pages, and extensions in modern pages.
4
-
ms.date: 06/22/2021
4
+
ms.date: 12/28/2021
5
5
ms.localizationpriority: high
6
6
---
7
-
# SharePoint Framework development with SharePoint Server 2019
7
+
# SharePoint Framework development with SharePoint Server 2019 & SharePoint Server SE
8
8
9
9
SharePoint Server 2019 supports SharePoint Framework client-side web parts in classic and pages, and extensions in modern pages.
10
10
11
+
> [!IMPORTANT]
12
+
> SharePoint Server Subscription Edition (SE) has all the same dependencies and requirements for the SharePoint Framework as SharePoint Server 2019.
13
+
11
14
## Which version of the SharePoint Framework to use
12
15
13
16
Because SharePoint Online and SharePoint Server 2019 have different release cycles for new capabilities, they also have different capabilities when it comes to the SharePoint Framework. SharePoint Online always uses the latest version of the SharePoint Framework, but SharePoint Server 2019 only supports the version that matches the server-side dependencies of the deployed packages.
@@ -24,18 +27,30 @@ If Internet access isn't available for the development machines, you can set up
24
27
25
28
The [Team-based development on the SharePoint Framework](team-based-development-on-sharepoint-framework.md) guidance document includes different options for development environment setup including when you might need to support multiple SharePoint Framework versions.
26
29
27
-
### Node.js, Gulp & Yeoman versions
30
+
### Node.js, Gulp, & Yeoman versions
28
31
29
32
The dependencies for SPFx v1.4.1 frameworks, tools, and the associated versions don't match the same dependency matrix for the latest versions of SPFx. In these cases, you may need to install specific versions of the tools.
30
33
31
34
For example, Gulp v3.* is only supported up to Node.js v10, while Gulp v4.* is supported from Node.js v12 and higher. Because SPFx v1.4.1 is only supported on Node.js v6 and Node.js v8, you need to ensure you have an older version of Node.js installed as well as an older version of Gulp & Yeoman.
32
35
33
-
If you're building SPFx v1.1 solutions, install the following specific versions of Gulp & Yeoman:
36
+
> [!NOTE]
37
+
> The Gulp team introduced a separate package, [gulp-cli](https://www.npmjs.com/package/gulp-cli), that should be installed globally. It can be used by projects that use either Gulp v3 & Gulp v4.
38
+
>
39
+
> Learn more about the gulp-cli here: [gulpjs/gulp/#2324](https://github.com/gulpjs/gulp/issues/2324).
40
+
41
+
Microsoft recommends using the most recent version of the Yeoman generator for the SharePoint Framework ([@microsoft/generator-sharepoint](https://www.npmjs.com/package/@microsoft/generator-sharepoint)) that supports creating on-premises projects: SPFx v1.10.1.
42
+
43
+
> [!IMPORTANT]
44
+
> The Yeoman generator for the SharePoint Framework, starting with v1.13.0, only supports projects for SharePoint Online. Learn more about this change in the [SharePoint Framework v1.13 release notes](release-1.13.md). However, SPFx 1.4.1 only supports up to Node.js v10. Therefore, you need to get the latest version of the Yeoman generator for the SharePoint Framework (v1.10.0) that works on the same version of Node.js (v10) that SPFx v1.4.1 is supported on.
0 commit comments