Microsoft has announced the general availability of SharePoint Framework (SPFx) version 1.22, a release centred on modernising the build and tooling experience for SPFx developers. This shift marks a foundational update to how SPFx solutions are built, aimed at addressing technical debt, improving extensibility, and aligning with broader Microsoft toolchain standards.
Prior to this release, SPFx projects leveraged a Gulp‑based build toolchain to orchestrate tasks such as compilation, bundling, and packaging. While familiar, this model has long been considered dated relative to modern JavaScript and TypeScript workflows. At the same time, older SPFx templates and generator outputs triggered npm audit vulnerabilities and lagged behind current dependency expectations. Version 1.22 addresses both concerns by transitioning to a new toolchain and cleaning up scaffolded solution vulnerabilities.
At the heart of the SPFx 1.22 update is the transition from a Gulp‑based to a Heft‑based build toolchain. Heft (a config-driven build orchestrator from the Rush Stack ecosystem) now manages build tasks for new SPFx projects, while underlying bundling continues to use Webpack. This shift aligns SPFx development with contemporary build ecosystems, enabling better extensibility, clearer configuration surfaces, and alignment with other Microsoft 365 toolchains. Existing projects upgraded to 1.22 can continue using the legacy Gulp workflows if needed, but new projects generated with Yeoman default to Heft.
Heft’s introduction addresses long-standing developer concerns about the SPFx toolchain being a ‘black box.’ According to Microsoft, Heft’s opinionated and plugin-capable design allows for more transparent, maintainable builds and facilitates future tooling enhancements. It supports shared configurations (rig.json), streamlined TypeScript settings, and native Webpack configuration options. However, migrating away from custom gulpfile.js implementations will require significant adjustments, particularly for teams using bespoke build steps.
Another important modernisation in this release is the resolution of all known npm audit reported vulnerabilities in both the SPFx Yeoman generator and the scaffolded project outputs. After scaffolding a new project with the latest generator, developers should no longer see high‑severity issues reported by npm audit, improving security baseline confidence out of the box. Microsoft also reset the default TypeScript version to 5.8 in scaffolded templates, giving developers access to more recent language features and improved tooling support.
The release doesn’t introduce any deprecations for previously supported APIs. However, Microsoft notes that only critical fixes will be applied to the legacy Gulp system going forward. In SPFx 1.23, new projects will use Heft exclusively (pending CLI readiness), and by SPFx 1.24, the Gulp-based pipeline will become officially unsupported.
Community response across social channels underscores both excitement and caution. On LinkedIn, members of the Microsoft 365 Developer community highlighted the significance of the build system change, noting that this "e;is not one of those simple updates"e; despite the semantic version number, especially because of the gulp‑to‑Heft shift. Some developers are already sharing walkthroughs and resources to help others adapt to the new Heft workflows. Others have mentioned that transitioning established projects represents a non‑trivial effort, particularly for teams with custom Gulp tasks or extensions, and are discussing strategies for incremental migration.
Looking forward, SPFx’s roadmap includes further CLI decoupling, open-sourcing templates, and deeper integration with Rush Stack tooling. Developers are encouraged to explore Heft now to ease future transitions and align with Microsoft’s direction.
For full release notes and Heft migration guidance, see SPFx 1.22 release notes and toolchain documentation.