Microsoft has announced the general availability of its SharePoint Framework. The project features a Page and Part model that allows for modern client-side development, simple Microsoft Graph integration and support for open source tools.
SharePoint Framework 1.0 Changelog
Naturally, this release comes with some new functionality. Though the changes are minor since the release candidate, they’re still important. Here’s the full list:
- “There are only a few changes in the actual framework code. The bulk of our work between RC0 and GA had to do with stability and future-proofing. It is our explicit goal that the parts you create today should continue to work for years to come. But fixes made to the underlying service continue to be supplied without issues, we don’t have 7 different minor and patch versions of framework code loaded, etc. There is still some work to do in this area for some components – we’ll get to those.
- The biggest change to the code itself is that we incorporated the strict null checks flag into SPFX, meaning that you can also enable this flag in your projects. It changed the API slightly, but should only be noticed if you enable strict null checks yourself.
- The other noticeable changes are in the default code that is generated by running yo. 1.0.0 is the version of the packages (woot!). We now reference @types with a strict version (no more lodash errors).
- We have feature XML support (along with upgrade). This can be used to provision needed fields, content types and lists for the web part in “elevated” mode. We’ll write up some posts on this in more detail.
- We have finalized the serialization format on classic pages. You should delete and re-add your webparts. We’ll support the old serialization format for a short while, then it will cease to work.”
Unfortunately, the GA release does come with one function disabled. The react template for office-ui-react has been removed for future proofing. Microsoft expects it to be re-implemented in a couple of weeks.
Until then, devs can get the latest npm packages and use them in the local workbench. However, Microsoft warns that server code rollout will happen over the next few days and that projects built with other packages won’t after a week or two.
You can find more detail about the changes on the SharePoint Framework GitHub.