After years of requests from the developer community, Microsoft has finally published a public roadmap for the SharePoint Framework (SPFx). This announcement, released on September 26, 2025, marks a significant shift in how Microsoft communicates its plans for the platform and includes some major changes that will impact most SPFx developers.
SPFx is powering the future of Microsoft 365. From AI-driven portals to seamless integrations across SharePoint, Teams and Viva, SPFx is driving innovation at scale. This new blog series kicks off our journey into the next evolution—transparent, community-driven, and built for the AI era. Let's shape what's next, together.
https://devblogs.microsoft.com/microsoft365dev/sharepoint-framework-spfx-roadmap-update-september-2025/
This is a comprehensive look at Microsoft’s announcement. In this article, I cover the following things:
- Microsoft published the first public SharePoint Framework roadmap, detailing plans through May 2026
- SPFx v1.22 (October 2025) replaces gulp with Heft + Rushstack + webpack, requiring migration work for existing projects
- Microsoft announced an 11-member SPFx Community Advisory Committee of MVPs to provide guidance on future development… and I’m on it!
- A new SPFx CLI will replace the Yeoman generator, and project templates will be open-sourced
- Migration documentation is being developed to help developers transition to the new build toolchain
- Answers to your most frequently asked questions
OK… let’s get to it!
What’s in the roadmap
The roadmap announcement covers three upcoming releases:
- SPFx v1.22 (October 2025): Focuses entirely on build toolchain modernization
- SPFx v1.23 (February 2026): Introduces new features, capabilities, and modernization of the new project creation experience
- SPFx v1.24 (May 2026): Additional feature additions and improvements
This is the first time Microsoft has provided this level of transparency about SPFx’s future direction. For years, the community has asked for a public roadmap… I personally have been begging them for years for this… and it’s encouraging to see Microsoft finally delivering on this request.
SharePoint Framework Roadmap: Next 3 releases over next 8 months
Got Questions? I'm Sure You Do!
I cover a lot in this article, but I’m sure you’ll have questions. That’s cool… fire them at me!
Leave your questions in the comments at the end of this article and I’ll be sure to get back to you!
The big change: build toolchain overhaul
The most significant update coming in SPFx v1.22 (due in October) is an overhaul of the build toolchain. Microsoft is removing gulp and replacing it with a pure Heft + Rushstack + webpack setup.
Here’s what’s changing:
- gulp is out: The task runner that’s been part of SPFx since the beginning is being removed
- Heft is in: Microsoft’s internally developed task runner replaces gulp
- Rushstack integration: The build process moves to Microsoft’s Rushstack monorepo tooling
- webpack remains: While the surrounding toolchain changes, webpack stays as the bundler
This isn’t just a minor update. It’s a fundamental change to how SPFx projects are built and configured. If you’ve customized your gulp tasks or build process, you’ll have work to do when migrating to v1.22.
I have mixed feelings about this change. On one hand, I’m glad to see gulp go. It’s old technology that much of the development community has moved away from. Personally, I’d prefer using npm scripts for running tasks.
On the other hand, they’ve replaced gulp with Heft, another task runner that’s open source but developed by Microsoft primarily for internal use. I’m not convinced that replacing one task runner with another, less widely-adopted task runner is a net-positive change for the community. It’s too early to say if this is a welcomed change or not… we need to start using it and at this point, it’s too early in the process to give a fair opinion.
Andrew Connell
Microsoft MVP, Full-Stack Developer & Chief Course Artisan - Voitanos LLC.
The good news is that Microsoft is positioning this as a smooth upgrade path. According to their announcement and conversations with the SPFx team, I don’t think you’ll need to make any changes to your SPFx business logic or components. In other words, when you migrate to SPFx v1.22, you shouldn’t have to touch your ./src folder. The changes are confined to the build configuration and toolchain.
New SPFx CLI replaces Yeoman
Along with the build toolchain changes, the next version of SPFx (v1.23 due in February 2026), Microsoft will introduce a new SPFx CLI to replace the current Yeoman generator approach. This new CLI aims to provide a more modern project scaffolding experience.
But that I’m a little unclear on is why we’re getting a CLI AND according to the roadmap, they are also modifying the Yeoman generator to open sourcing the project templates. That means the community will be able to contribute improvements and additions to the official project templates. This is a welcome change that should lead to better, more community-driven starter templates.
But why both? At this time, that’s not clear.
Addressing npm audit issues
One of the highlighted improvements is addressing npm audit security issues in the dependency tree. This has been a persistent pain point for SPFx developers, with audit warnings appearing in virtually every project.
That’s quite a big goal… especially considering this has been such a long-standing issue. Today, if you create a brand new SPFx v1.21.1 project with a single React-based web part, you get 79 vulnerabilities with different severity:
Result of npm install after creating a brand new SPFx v1.21.1 project with a single React-based web part
I want to be clear about what’s actually happening with npm audit issues. The roadmap announcement includes language about “addressing all npm audit issues,”. I checked and yes, that’s what Microsoft’s intent is: to eliminate all issues that are reported when you do an npm install.
Microsoft is updating dependencies, which will reduce audit findings. Even if they do eliminate all issues at the GA release in October 2025, there’s a long gap until v1.23 in February 2026. New audit findings will inevitably appear during that time. They have said any major security vulnerabilities found in dependencies will be addressed with updates between the two releases.
We’ll see if they get to 0 vulnerabilities… that’s quite an ambitious goal.
Andrew Connell
Microsoft MVP, Full-Stack Developer & Chief Course Artisan - Voitanos LLC.
That said, any reduction in audit warnings is a positive step. The current state of npm audit findings in SPFx projects is frustrating, and even partial improvements are better than the status quo.
Open sourcing templates and tooling
Microsoft is making several components of the SPFx development experience open source:
- Project templates: The Yeoman generator templates will be open-sourced
- Build tooling: More of the build pipeline will be transparent and community-accessible
- Documentation: Enhanced documentation for the new toolchain (which I’m currently helping Microsoft develop)
This move toward transparency and community involvement is exactly what the SPFx ecosystem needs. Open-sourcing these components allows the community to contribute improvements, identify issues faster, and understand exactly how the platform works.
SPFx Community Advisory Committee
Microsoft also announced the formation of an 11-member SPFx Community Advisory Committee, composed entirely of Microsoft MVPs.
I’m honored to be included in this group!
The committee’s role is to provide guidance and feedback to Microsoft on SPFx’s direction, priorities, and developer experience. This is another positive step toward better communication between Microsoft and the developer community.
Having a formal channel for community input should help Microsoft make more informed decisions about the platform’s future and avoid some of the missteps that have frustrated developers in the past.
What about SPFx on-premises?
There’s been no mention of SharePoint on-premises in this roadmap, and that’s not surprising. Microsoft has essentially stopped active development on SPFx for on-premises environments.
They attempted a few updates in the past that went poorly during rollout… I’ve written extensively about these previously:
For the first time in 7 years, Microsoft has updated the installed version of the SharePoint Framework in an on-premises SharePoint Server deployment!
https://www.voitanos.io/blog/sharepoint-framework-updated-in-sharepoint-server-subscription-edition/
Learn the implications of the SharePoint Server SE 23H2 feature update for SPFx projects. A downgraded SPFx & bad guidance on customizing projects.
https://www.voitanos.io/blog/sharepoint-framework-sharepoint-server-subscription-edition-23h2/
The SharePoint Server Subscription Edition feature update 23H4 is out, but this time it doesn't include any changes to SharePoint Framework.
https://www.voitanos.io/blog/sharepoint-framework-sharepoint-server-subscription-edition-24h1/
It appears they’ve decided not to invest further in the on-premises experience. If you’re building SPFx solutions for on-premises SharePoint, you shouldn’t expect any new features or updates beyond what’s already available.
Migration concerns and questions
The build toolchain changes raise several important questions about migration:
Will upgrades be painful?
According to Microsoft, they’re working to make the upgrade process as smooth as possible. The engineering team is focused on ensuring developers can migrate without significant pain. However, the reality is that if you’ve customized your build process or gulp tasks, I fully expect that you’ll have work to do to migrate.
In other words, if you made any edits to the ./gulpfile.js by to create custom tasks or to modify the webpack configuration object, expect some migration work. For example, I’m working through how these changes will impact some of my changes that I’ve written about in the past, including managing the sourcemap creation or keeping secrets out of your code using the WebPack define plugin:
This step-by-step guide explains how to overcome SPFx production debugging challenges using source maps with a custom webpack configuration and gulp tasks.
https://www.voitanos.io/blog/sharepoint-framework-how-to-debug-solutions-in-production-using-source-maps/
Here's a post that teaches you a technique that you can start leveraging in your SharePoint Framework (SPFx) projects right away!
https://www.voitanos.io/blog/leverage-webpack-define-plugin-spfx/
Will builds be faster?
Microsoft’s stated objective is to improve build performance with the new toolchain. However, in the current beta builds, I’m not seeing performance improvements yet. In fact, builds are currently slower. The team is working on optimizations for future beta releases, but we won’t know the real performance story until the GA release in October.
Can you keep using gulp?
Microsoft has indicated that you can elect to keep using gulp “for now,” but it’s unclear if this is a temporary option or something that will be supported long-term. The uncertainty around this is concerning for teams with heavily customized build processes.
Andrew Connell
Microsoft MVP, Full-Stack Developer & Chief Course Artisan - Voitanos LLC.
What about custom build configurations?
If you’ve created custom gulp tasks, customized the webpack configuration, or modified your build configuration significantly, you’ll need to determine how to replicate that functionality with Heft. Whether this will be straightforward or require significant rework remains to be seen. I’m working with Microsoft on the migration documentation, so as I learn more, I’ll share what I discover.
Timeline and availability
Here’s when you can expect these changes:
- October 2025: SPFx v1.22 GA release with new build toolchain
- February 2026: SPFx v1.23 with new features and capabilities
- May 2026: SPFx v1.24 with additional improvements
The v1.22 beta is already available for testing, though it’s still rough around the edges. If you want to prepare for the transition, I’d recommend waiting until later beta releases when more of the issues are resolved and the migration path is clearer.
Impact on my SPFx courses
These changes will have a significant impact on my industry-leading Mastering the SharePoint Framework course, including my own. The build toolchain changes, new CLI, and open-source templates affect multiple lessons and chapters in existing SPFx courses.
I’m currently working through how I’ll update my courses to reflect these changes. The updates will be spread out over several months as the new features mature and the community develops best practices around the new toolchain.
When I have more concrete plans for course updates, I’ll share them with my student community first in Voitanos Learn. Just know that I’m on it!
What this means for you
If you’re currently building SPFx solutions, here’s what you should do:
In the short term: Continue building with the current SPFx version. The v1.22 beta isn’t stable enough for production work yet, things will change, and the migration path isn’t fully documented. Right now, just sit back and keep an eye on the changes. The best way to keep aware of this: subscribe to my newsletter, subscribe to my articles (blog), & follow me on LinkedIn.
Start planning: If you have heavily customized build processes, inventory what you do… from custom gulp tasks to webpack config modifications. You will have work to do… but it’s not clear exactly what that is. So having an inventory will help.
What Kinds of Build Toolchain Mods Have You Done?
Let me know by sharing the kinds of things you do in the comments of this article!
I’m working with Microsoft on the documentation for this change and ensuring the build toolchain changes won’t introduce any blockers so the more scenarios you share, the more we can help!
Watch for updates: I’m working with Microsoft on the migration documentation, and I’ll be sharing insights and guidance as I learn more. Follow my blog and social channels to stay updated on the latest information.
Test when ready: Once later beta releases are available and the migration documentation is published, test the upgrade process with non-critical projects. This will help you understand the effort required for your production solutions.
Frequently asked questions
Based on conversations with developers in my community and on social media, here are answers to the most common questions about this announcement:
Q: Will upgrading to SPFx v1.22 require changes to my source code?
Based on what I’m seeing in the beta and discussions with the SPFx team, you shouldn’t need to make changes to your ./src folder when upgrading to v1.22. The changes are focused on the build toolchain and configuration files. That said, I’m still working with Microsoft to fully understand the migration process, so this could change as we get closer to the GA release.
Q: Can I keep using my existing gulp configuration?
Microsoft has indicated you can elect to continue using gulp, but it’s unclear if this is a permanent option or temporary bridge. The language they’ve used suggests it might be a “for now” situation. As I said above, I think if you upgrade to SPFx v1.22, you should migrate these changes to the new toolchain and not try to bring forward your gulp modifications as I consider that a dead-end path… you’d just be “kicking the can down the road” to deal with it later.
Q: Will the new toolchain actually eliminate npm audit issues?
According to Microsoft, yes. But in my opinion, I think that’s more of an aspiration. We’ll see if they get there, but I find it hard to trust the SPFx v1.22 toolchain will have zero findings when SPFx v1.22 goes GA in October.
I hope I’m pleasantly surprised and admit I was wrong, but… well… after 8 years of SPFx releases, let’s just say my expectations are conditioned this way.
Q: Will builds actually be faster with the new toolchain?
That’s the objective, that’s what they say, and one of the key reasons Microsoft is making these changes. However, in the current beta builds I’m testing, I’m not seeing performance improvements — builds are actually slower right now in the current beta. The team is working on optimizations for future betas, but beta performance isn’t what matters. We won’t know the real performance story until the GA release in October.
Q: What happens to SPFx on-premises?
Nothing. There are zero plans to continue updating SPFx for on-premises SharePoint. Microsoft attempted a few updates in the past that didn’t go well, and they’ve essentially abandoned further development for on-premises environments. If you’re building for on-premises SharePoint, you’re stuck with the current feature set.
Q: Can I build my own build process using Vite instead of webpack?
This is something I’m very interested in exploring. Right now, I believe it’s theoretically possible to build your own custom build process, but whether there will be easy tooling to support this remains to be seen. The question of whether first-party plugins and solutions will be available for alternative build tools is still open. Once I understand the new system better, I’ll experiment with this and share what I learn.
You can bet I’ll have an article showing how to do this once I get it figured out!
Q: What about new and edit panel overrides for lists?
This roadmap item refers to enabling new and edit forms to appear in a side panel rather than taking users to a separate page. However, the exact implementation details aren’t entirely clear yet. I’m working to get more clarity on this as the feature develops.
Q: How customizable will the new Heft-based build system be?
If you’ve created custom gulp tasks or heavily modified your build configuration, you’ll have work to do with the new system. I’m still working with Microsoft to understand exactly how extensible the new Heft-based system is and what customization options will be available.
The migration documentation I’m helping create for the official SPFx documentation will cover this, but right now there are still aspects I don’t fully understand.
Q: Should I wait to start new SPFx projects until v1.22 is released?
No, continue building with the current SPFx version. The v1.22 beta isn’t stable enough for production work, and the migration path isn’t fully documented yet. When v1.22 reaches GA in October 2025, you’ll be able to upgrade your existing projects. Starting new projects now won’t put you at a disadvantage.
The only thing I would caution is that if you are working on a complex build toolchain modification, I’d push that off as long as you can. I can’t see how anything you do today won’t have to be re-engineered when SPFx v1.22 is released. Plus, it’s still too early to say how significant the re-engineering task will be.
Q: Will there be breaking changes in v1.22 beyond the build toolchain?
Based on current information, v1.22 is focused exclusively on build toolchain changes. There shouldn’t be breaking changes to SPFx APIs or features. The breaking changes come in how your projects are built and configured, not in the framework itself.
Final thoughts
The publication of a public SPFx roadmap is a significant and welcome change in how Microsoft communicates with the developer community. The fact that they’re also forming an advisory committee and open-sourcing key components shows they’re serious about improving the SPFx developer experience.
However, the build toolchain changes coming in v1.22 are substantial. While Microsoft is positioning them as improvements, the reality is that they’ll require work from developers who have customized their build processes. The move from gulp to Heft in particular raises questions about whether we’re trading one niche task runner for another.
I’m cautiously optimistic about these changes. The transparency is exactly what the community has been asking for, and the technical improvements have clear objectives. But as with any major platform change, the proof will be in the execution.
I’m working directly with Microsoft on the migration documentation for v1.22, specifically around the build toolchain changes. As I learn more and gain a better understanding of the migration path and implications, I’ll share that information with you through blog posts, course updates, and community discussions.
What questions do you have about these changes?
What concerns you most about the upcoming updates?
Let me know in the comments below or reach out to me on social media. Your questions help me focus my work on the documentation and ensure I’m addressing the issues that matter most to the community.
Microsoft MVP, Full-Stack Developer & Chief Course Artisan - Voitanos LLC.
Andrew Connell is a full stack developer who focuses on Microsoft Azure & Microsoft 365. He’s a 21-year recipient of Microsoft’s MVP award and has helped thousands of developers through the various courses he’s authored & taught. Whether it’s an introduction to the entire ecosystem, or a deep dive into a specific software, his resources, tools, and support help web developers become experts in the Microsoft 365 ecosystem, so they can become irreplaceable in their organization.
