Generally Available: SharePoint Framework (v1.0)

Cross-posted on Andrew Connell's blog: Generally Available: SharePoint Framework (v1.0)

Yesterday Microsoft announced that the SharePoint Framework has reached the Generally Available milestone. That means we're at v1! The development tools have been updated to v1 and the v1 bits are rolling out to Office 365 SharePoint Online tenants now. Microsoft said it will take about a week or so for it to reach all Office 365 tenancies.

You can get the details of this update from their wiki page in the main sp-dev-docs repo. So what change from RC0 to GA?

• As expected, they did a lot of bug fixes, stability, and "future-proofing" work... not exactly sure what "future-proofing" means but sounds buzz-wordy.
• Added struct null checks within SPFx which means you can add this to your projects. That impacted the API slightly but developers will only be impacted if they also elect to enable strict null checks.
• All build toolchain packages from SPFx & Microsoft are now v1.0.0 and TypeScript @types are referenced using explicit versions. If only that was done earlier developers wouldn't have been hit with that lodash type mismatch issue. At least the team learned from that mistake!
• Client-side web parts work on classic pages again. The team changed the serialization format on classic pages which fixed some issues adding them to pages.

One interesting thing they did was remove the Office UI Fabric React from the ReactJS project template in the Yeoman generator. Apparently, there is additional work to do to future-proof this. They said it will take a few weeks. I'm not terribly clear on what the issues are or if you can use it. Thankfully someone has already asked the question so you can follow what the team says about this.

What's Next?

Check this post from earlier this week, What's Next for the SharePoint Framework, which summarized some roadmap stuff the team shared in a meeting last week.

In the release notes for GA they also mentioned two other upcoming features they plan to implement:

• Allow developers to specify the version of Office UI Fabric they are using. This enables developers to pick a specific version and not use any newer version that may introduce a breaking change.
• Enable developers to include only parts of the Office UI Fabric ReactJS implementation to be incorporated statically into a package so you can keep the packages small & isolate yourself from future updates.

My question, what about React? Late last year I asked the team about this. Now that we're at GA, Microsoft really needs to address this.

At any rate, congrats to the team & check out their announcement blog post: Office Blogs: SharePoint Framework reaches general availability