The Future of SPFx Scaffolding: Roadmap, GA Timeline, and What’s Coming Next

/ Sudharsan K...

@microsoft/spfx-cli is in pre-release today. GA was targeted for September 2026 — this month — but as of this writing the CLI is still at 0.1.0-pre.3 and the SPFx release it’s tied to is still in public preview, so that date looks increasingly likely to slip (see the note below). Once GA lands, whenever that is, it will become the officially recommended scaffolding tool for SharePoint Framework, and the Yeoman generator will receive its final update and step back.

This post covers what happens between now and GA, what comes after, and what SPFx developers should know to prepare.

The Three Phases

The @microsoft/spfx-cli development roadmap is organized into three phases. Phase 1 is complete. Phase 2 is in progress, with GA nominally targeted for September 2026 — though that date now looks likely to slip (see Phase 2 below). Phase 3 is post-GA.

Phase 1 — Core Foundation (Complete)

Phase 1 established the architectural foundation for everything that follows. It is complete as of the pre-release in March 2026.

What was delivered:

  • Rush monorepo structure — The tool is built on the RushStack ecosystem, giving it a maintainable, consistent build and dependency management structure
  • Scaffolding API — The @microsoft/spfx-template-api core engine that renders templates with name casing, substitution, and file generation
  • Template migration — All 17 official SPFx templates migrated from the Yeoman generator to the open-source GitHub repository, with community access
  • spfx create command — The primary scaffolding command with full flag support
  • Runtime template fetching — Templates fetched from GitHub at scaffold time, not bundled in the CLI

Phase 1 proved the architecture. The tool already covers the core new-project scaffolding use case that most developers need.

Phase 2 — Governance and Core Functionality (In Progress, Targets GA)

Phase 2 remains in development as of September 2026 — no version of @microsoft/spfx-cli has shipped since 0.1.0-pre.3 in April. This phase targets the features and quality bar required for GA, still nominally scheduled for this month. Microsoft’s own sources disagree on which SPFx release GA is tied to (SPFx 1.24 per the more recent developer-blog roadmap update, SPFx 1.25 per the Microsoft Learn roadmap page), and SPFx 1.24 itself is still in public preview (beta.3, August 27, 2026) — so the September target looks increasingly likely to slip regardless of which version number it lands on.

NPM Publishing and CI/CD Infrastructure

The publishing workflow and CI/CD pipeline for the CLI itself is being formalized in Phase 2. This ensures reliable, consistent releases through the GA milestone and beyond.

list-templates Command

The spfx list-templates command — already available in pre-release — is being finalized in Phase 2. The GA version will include stable output formats and potentially structured output for scripting (related to issue #235 — JSON output mode).

Merge Helpers — The Most-Requested Missing Feature

The most impactful Phase 2 deliverable for most SPFx developers is MergeHelpers: support for adding new components to an existing SPFx project.

Currently, if you want to add a second web part or a new extension to an existing project, you must use yo @microsoft/sharepoint. @microsoft/spfx-cli only scaffolds new solutions today.

Merge helpers will change this. They will handle the non-trivial merging required when adding a component to an existing project:

  • Merging package.json dependencies without conflicting with existing packages
  • Merging config/config.json to add a new bundle entry
  • Adding new files to src/ without overwriting existing component code

This is a technically complex feature — getting it right is more important than getting it fast. When merge helpers land, @microsoft/spfx-cli will fully replace the Yeoman generator for all standard scaffolding workflows.

CI Coverage

Phase 2 includes improving the automated test coverage for the CLI and its templates. Correctness in the generated scaffold output is critical — the GA release needs high confidence that every template produces buildable, correct projects across all supported Node versions.

Phase 3 — Stabilization and Expansion (Post-GA)

Phase 3 is the post-GA roadmap. These features are not yet available and their exact timing is not confirmed, but they are documented in the official architecture plan.

npm create @microsoft/spfx

A front-end for npm create (also known as npm init) will make project scaffolding available without a global CLI install:

npm create @microsoft/spfx@latest \
  --template webpart-react \
  --library-name my-lib \
  --component-name "Hello World"

This pattern — running scaffolding without a persistent global install — is increasingly common in the JavaScript ecosystem (npm create vite, npm create next-app, etc.). An npm create front-end would align SPFx scaffolding with modern JavaScript tooling conventions.

MCP Server Front-End

This is the most forward-looking item in the Phase 3 roadmap, and it deserves attention.

The architecture plan includes a Model Context Protocol (MCP) server front-end for @microsoft/spfx-cli. MCP is the protocol used by AI agents — including GitHub Copilot, Claude, and similar tools — to invoke external tools and services.

An MCP server front-end would mean that AI coding assistants could scaffold SPFx projects directly, without leaving the editor and without the developer typing CLI commands manually:

  • A developer asks GitHub Copilot: “Create a new React web part for my SPFx project”
  • Copilot invokes the MCP server, which calls the SPFx scaffolding engine
  • The scaffolded files appear in the project immediately

This represents a meaningful shift in the SPFx development experience. Scaffolding becomes a first-class AI-assisted operation rather than a separate, manual tooling step. The open-source template model in @microsoft/spfx-cli is what makes this viable — the AI agent can understand what templates are available and what parameters they require by inspecting the public GitHub repository.

Yeoman Compatibility Shim

For teams with scripts or tooling that invoke yo @microsoft/sharepoint, Phase 3 includes a Yeoman compatibility shim. This would allow the same command patterns to invoke @microsoft/spfx-cli under the hood, providing a smoother migration path for teams that cannot immediately rewrite their scaffolding scripts.

Per-Template CLI Parameters

Phase 3 also includes support for template-specific CLI parameters. Currently, all templates share the same set of flags. Some templates could benefit from template-specific options — for example, an ACE template might have parameters for card layout or data source configuration that are not meaningful for a web part template. Per-template parameters would allow the CLI to expose these without polluting the global flag space.

Third-Party Template Ecosystem

Phase 3 envisions a discoverable third-party template ecosystem. Community and organization templates would become easier to find and use, similar to how npm create front-ends allow template discovery from the npm registry.

The SPFx Release Milestones

ReleaseTarget DateWhat It Means
SPFx 1.23March–May 2026@microsoft/spfx-cli preview launched (current)
SPFx 1.24September 2026 (target — see note)@microsoft/spfx-cli GA — primary recommended tool
Post-GALate 2026Yeoman generator receives final update — no further development

Note (updated September 2026): Microsoft’s own published sources disagree on which SPFx release the CLI’s GA is tied to — a more recent developer-blog roadmap update names SPFx 1.24, while the Microsoft Learn SPFx roadmap page still names SPFx 1.25. Either way, SPFx 1.24 itself remains in public preview (beta.3 as of August 27, 2026) and @microsoft/spfx-cli is still at 0.1.0-pre.3, unchanged since April — so the September 2026 GA target looks increasingly unlikely to hold. Treat the date in this table as the last officially stated target, not a confirmed timeline.

Teams that start learning and adopting @microsoft/spfx-cli now will still be well-positioned whenever the official recommendation changes, regardless of exactly which month or version number GA lands on.

Yeoman End-of-Life

@microsoft/generator-sharepoint will not be immediately removed after the CLI’s GA release. Microsoft has stated it will receive a final update after GA. The Yeoman generator will continue to exist on npm and will continue to scaffold projects, but it will not receive further feature development or template updates.

Timeline expectations:

  • Now, and for as long as GA is pending: Both tools are available. @microsoft/spfx-cli is recommended for new projects.
  • After GA (still nominally targeted for September 2026, see the note above): @microsoft/spfx-cli is the official recommendation. Yeoman generator is in maintenance-only status.
  • Long-term: New SPFx versions and template updates will be reflected in @microsoft/spfx-cli only. Yeoman templates will not be updated to match.

If you continue using the Yeoman generator after the GA milestone, your scaffolded projects will still work — SPFx solutions do not have a runtime dependency on the scaffolding tool. But the templates you scaffold from will become increasingly out of date as SPFx evolves.

How to Participate Today

The most meaningful way to shape the direction of @microsoft/spfx-cli before GA is to engage with the open-source repository:

File Issues

If you find something that does not work as expected — a bug in a scaffolded template, a missing flag, confusing error output — file an issue at https://github.com/SharePoint/spfx/issues. The team is actively responding to pre-release feedback.

High-impact open issues at time of writing:

  • #237 — --version flag missing
  • #235 — JSON output mode for scripting
  • #98 — Per-template CLI parameters

Note: Issue #246 (--library-name optional for some template types) was resolved by August 2026.

Contribute Templates

The templates are in the SharePoint/spfx repository and contributions are welcomed. If you find an incorrect TypeScript configuration, an outdated dependency version, or a template pattern that does not reflect current best practices, a pull request is the fastest path to a fix.

Test Pre-Release Versions

The most valuable thing early adopters can do is scaffold real projects using the pre-release CLI and report what they find. Every issue filed before GA reduces the bug surface at release.

What This Means for Your Team

If you have followed this five-part series, you now have a complete picture of @microsoft/spfx-cli:

  • Why it exists: Yeoman’s structural problems drove the need for a purpose-built replacement
  • How it works: Runtime template fetching, open-source MIT templates, flag-based interface
  • How to use it: Installation, templates, flags, build workflow
  • How it compares: Where it is already better, where Yeoman still leads temporarily
  • Enterprise patterns: Custom templates, CI/CD, air-gapped builds, programmatic API
  • What is coming: Merge helpers, MCP server, npm create front-end, Yeoman end-of-life

GA was nominally targeted for September 2026 — this month — but as of this writing it has not landed, and the target looks increasingly likely to slip (see the roadmap note above). The pre-release is stable enough for new project scaffolding today. There is no reason to wait until GA to start building familiarity with the tool.

Resources

The Complete Series

Leave a Reply