The SharePoint Framework (SPFx) is coming up on its 5th anniversary of the v1 release in just over a month!
From the very first release, I keep seeing one question keeps coming up about a concept that confuses developers. This is a simple concept, one that could have been avoided with a better naming decision many years ago. In this post, I’m going to attempt to clear it up.
In this post, I cover:
- What’s the problem?
- Yeoman generator for the SharePoint Framework
- SharePoint Framework runtime, libraries, & dependencies
- “OK, makes sense! So why do people get confused?”
- Scenario: Upgrading SPFx projects
- Scenario: Working with on-premises SharePoint deployments
Since the #SharePoint Framework initial v1 release, I’ve seen questions coming up about a concept that confuses developers. This is a simple concept, once understood, should help. In this post, I’m going to attempt to clear it up. #SPFx #Microsoft365Dev https://t.co/6WUJxoTcq6 pic.twitter.com/WzH9aw2FlJ— Voitanos (@voitanos) January 4, 2022