Guide: Microsoft Fabric Enables Real-time Analytics
Development
- 23 Dec, 2025
- 13 Views
- 0 Comment
The release of the SharePoint Framework (SPFx) v1.22 is now available, and it’s a huge one. This release doesn’t include any new features or fixes, in contrast to earlier releases that did. Rather, three significant modifications to the “behind the scenes” component of SPFx projects are included in this release:
- Finally, clean npm audit reports
- Upgrade to TypeScript v5.8
- A new build toolchain based on Heft
Let’s examine the latest developments and their implications for your development process.
What’s New?
Clean npm audits
If you have worked as an SPFx developer for any amount of time, you are probably aware of the several npm package vulnerabilities that have been reported. Many of these vulnerabilities are classified as high or critical, and they are all connected to dependencies that are located deep within the Microsoft toolchain packages.
Microsoft spent a lot of time updating dependencies for SPFx v1.22 in an effort to remove the need to run npm audits on your project after installing dependencies.
This is significant because, even in cases where the susceptible packages only run during development and never reach production, security teams at corporate firms frequently identify these vulnerabilities during code reviews. You may now present a flawless audit report with assurance.
TypeScript v5.8 by default
TypeScript v5.8 is used by default in new projects scaffolded with SPFx v1.22. This is a big improvement over earlier iterations and includes all the contemporary TypeScript features you’ve been lacking.
Significant toolchain redesign: switching from Gulp to Heft
Even while it might not seem like much, this release will have the greatest impact. Project development has undergone a dramatic change with the release of SPFx v1.22. A Heft-based toolchain will take the place of the outdated gulp-based toolchain that SPFx has used since version 1.0 in 2017.
The main topic of this blog is to highlight the new features of SPFx v1.22 version.
What’s your take on these changes? Are you planning to move to the new toolchain now, or will you wait? Share your migration approach in the comments and join the conversation.
