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/design/use-brand-center-fonts-in-spfx-components.md
+5-2Lines changed: 5 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Use SharePoint brand center fonts in SharePoint Framework solutions
3
3
description: Developers can use the fonts defined in Brand center in their SharePoint Framework (SPFx) components. This article demonstrates how you can use the fonts defined in the SharePoint brand center in your SPFx components.
4
-
ms.date: 10/07/2024
4
+
ms.date: 04/23/2025
5
5
ms.localizationpriority: high
6
6
---
7
7
@@ -109,9 +109,12 @@ To test the web part, start the local web browser, but don't launch a browser to
109
109
1. In the console, the **gulp serve** command will output a line that looks similar to the following:
110
110
111
111
```text
112
-
[spfx-serve] To load your scripts, use this query string: ?debug=true&noredir=true#debugManifestsFile=https://localhost:4321/temp/manifests.js
112
+
[spfx-serve] To load your scripts, use this query string: ?debug=true&noredir=true#debugManifestsFile=https://localhost:4321/temp/build/manifests.js
113
113
```
114
114
115
+
> [!NOTE]
116
+
> Debug query string was changed starting from the SPFx verson 1.21 from `https://localhost:4321/temp/manifests.js` to `https://localhost:4321/temp/build/manifests.js`
117
+
115
118
1. Open the browser and navigate to a page that you have permission to add a web part to the page.
116
119
1. Add the query string from the preceding console message to the URL and load the page.
description: Release notes for the SharePoint Framework v1.21 release.
4
-
ms.date: 04/10/2025
4
+
ms.date: 04/23/2025
5
5
ms.localizationpriority: high
6
6
---
7
7
# SharePoint Framework v1.21 release notes
8
8
9
-
This release has initial configuration updates for web parts in the context of flexible layouts in SharePoint and personalization option for cards. We're also looking to further include other technical updates before this version is generally available.
9
+
This release has updates on the Nodejs version and on other technical dependencies. It also contains updates for web parts in the context of flexible layouts in SharePoint and personalization option for cards.
10
10
11
11
> [!NOTE]
12
-
> [SharePoint Framework API Reference](https://learn.microsoft.com/en-us/javascript/api/overview/sharepoint?view=sp-typescript-latest)was also updated to match the latest 1.21 version as part of the beta 2 release.
12
+
> [SharePoint Framework API Reference](https://learn.microsoft.com/en-us/javascript/api/overview/sharepoint?view=sp-typescript-latest)has been also updated to match the latest 1.21 version.
@@ -49,13 +45,14 @@ In the project's **package.json** file, identify all SPFx v1.20 packages. For ea
49
45
50
46
### Node.js v22 support
51
47
52
-
Node.js support will be updated to the version 22 with the 1.21 release. This beta build is the first version to include version 22 support.
48
+
Node.js support has been updated to version 22 with the 1.21 release.
53
49
54
-
Notice that when SPFx 1.21 is generally available, Node.js version 22 is the only supported version with it. Currently SPFx supports Node.js version 18, which will fall out of the support in end of April 2025. We are planning to have SPFx 1.21 generally available before that date.
50
+
> [!NOTE]
51
+
> Notice that Node.js version 22 is the only supported version with version 1.21.
55
52
56
53
### TypeScript 5.x support
57
54
58
-
Starting with this first release candidate for the 1.21 release, we have also updated the support for the TypeScript 5.x. Default scaffolded projects are using currently specifically 5.3.3 version by default.
55
+
TypeScript has been updated to TypeScript 5.x. Default scaffolded projects are using currently specifically 5.3.3 version by default.
59
56
60
57
### Flexible layout configuration options for web parts
61
58
@@ -70,15 +67,15 @@ New flexible layout sizing options are introduced for the web part manifest. The
70
67
```
71
68
72
69
> [!NOTE]
73
-
> By default all custom web parts are supported in the flexible layout option and don't require any code level changes.
70
+
> By default, all custom web parts are supported in the flexible layout option and don't require any code level changes.
Viva Connections will start supporting end user configuration options for the dashboard. End users can add and remove cards from the dashboard based on their preference. Supported cards are explicitly enabled for this scenario and also custom cards are supported.
76
+
Viva Connections will start supporting end user configuration options for the dashboard. End users can add and remove cards from the dashboard based on their preference. Supported cards are explicitly enabled for this scenario and custom cards are supported.
80
77
81
-
By default personalization isn't allowed for the custom Viva Connections cards.
78
+
By default, personalization isn't allowed for the custom Viva Connections cards.
82
79
83
80
```json
84
81
"personalization": [
@@ -92,6 +89,20 @@ By default personalization isn't allowed for the custom Viva Connections cards.
92
89
93
90
Default [Teams JavaScript SDK](https://github.com/OfficeDev/microsoft-teams-library-js) version for the SPFx powered solutions has been updated to version 2.32.
94
91
92
+
## Changes
93
+
94
+
Default debugging URL location was changed as part of the release. `debugManifestsFile` is updated as `https://localhost:4321/temp/build/manifests.js`. This might have impact on any tooling or scripts which have previously taken a dependency on this URL. Please update your those accordingly with this change.
95
+
96
+
*Previous versions*
97
+
```
98
+
[spfx-serve] To load your scripts, use this query string: ?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/manifests.js
99
+
```
100
+
101
+
*Updated debugManifestFile URL starting from 1.21 version*
102
+
```
103
+
[spfx-serve] To load your scripts, use this query string: ?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/build/manifests.js
104
+
```
105
+
95
106
## Deprecations
96
107
97
108
No new updates.
@@ -102,6 +113,8 @@ No new updates.
102
113
103
114
## Feedback and issues
104
115
105
-
We're interested on your feedback around the release. Do let us know any findings or other feedback using the [SPFx issue list](https://github.com/SharePoint/sp-dev-docs/issues).
116
+
We're interested in your feedback about the release. Do let us know any findings or other feedback using the [SPFx issue list](https://github.com/SharePoint/sp-dev-docs/issues).
117
+
118
+
We will be doing some cleaning in the issue list after the 1.21 release to better focus on the latest issues and are more focused on helping you with any of your findings.
Copy file name to clipboardExpand all lines: docs/spfx/web-parts/get-started/build-a-hello-world-web-part.md
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Build your first SharePoint client-side web part (Hello World part 1)
3
3
description: Create a new web part project and preview it.
4
-
ms.date: 11/02/2023
4
+
ms.date: 04/23/2025
5
5
ms.localizationpriority: high
6
6
ms.custom: scenarios:getting-started
7
7
---
@@ -98,7 +98,7 @@ Build target: DEBUG
98
98
[12:13:24] Starting 'serve'...
99
99
[12:13:24] Starting gulp
100
100
[12:13:24] Starting subtask 'spfx-serve'...
101
-
[12:13:24] [spfx-serve] To load your scripts, use this query string: ?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/manifests.js
101
+
[12:13:24] [spfx-serve] To load your scripts, use this query string: ?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/build/manifests.js
102
102
[12:13:25] Starting server...
103
103
[12:13:25] Finished subtask 'spfx-serve' after 1.24 s
0 commit comments