SharePoint Framework 1.22 Ships with Heft-Based Build Toolchain and Refreshed Project Baseline
Briefly

SharePoint Framework 1.22 Ships with Heft-Based Build Toolchain and Refreshed Project Baseline
"Prior to this release, SPFx projects leveraged a Gulp‑based build toolchainto 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."
"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."
SPFx 1.22 introduces a fundamental toolchain modernization by moving new project builds from a Gulp-based workflow to Heft, while retaining Webpack for bundling. The update targets technical debt, obsolete templates, and npm audit vulnerabilities in scaffolded solutions. Heft provides a config-driven, opinionated, and plugin-capable orchestration model that exposes clearer configuration surfaces, supports shared rig.json settings, streamlines TypeScript configuration, and offers native Webpack options. Existing projects upgraded to 1.22 can keep legacy Gulp workflows, but Yeoman-generated new projects default to Heft, requiring migration from custom gulpfile.js implementations where present.
Read at InfoQ
Unable to calculate read time
[
|
]