Update SharePoint 2019 with the latest SPFx Drop
Update SharePoint 2019 with the latest SPFx Drop. Most of the SharePoint Customers still have an OnPremises Farm. If you want customers to adopt this pattern it must be available in both environments. Staying on drop 1.4.1 in SP 2019 is the death of SPFx
Anonymous
shared this idea
Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.
Let me provide some additional context of this to explain why we cannot do this. In short, it’s not just about supported SharePoint Framework version, it’s about dependency on all out-of-the-box web parts and UX implementation.
We would love to provide updated SPFx support for SP2019, but this is unfortunately impossible due the server-side dependencies and restriction.
SharePoint 2019 was created by forking SharePoint Online code while back. At the time the used SharePoint Framework for the out-of-the-box web parts and UX layer was SPFx 1.4.x with the related server-side dependencies, which is then setting the used SPFx version even for now. As SharePoint 2019 is using more than 2 years older out-of-the-box UX layer than SharePoint Online, there is unfortunately now way for us to provide an update for it.
We absolutely understand the frustration what this technical dependency is providing. To be honest, we are as frustrated on the situation as you are, as we would love to help with this. As we cannot update your server-side implementation without doing full end-to-end version refresh of the whole SharePoint on-premises version, we cannot also update the supported SharePoint Framework. Just to be clear – full refresh would mean completely new SharePoint on-premises major version.
Will we update the used SPFx version for the possible future on-premises versions? Potentially. There has not been any public decision on this for now.
9 comments
Comments are closed-
Patric Schielke
commented
Details have been delivered in the comments, is there any update from the SharePoint Dev Platform Team?
-
Francis Goeminne
commented
Unable to use any of the PNP search web parts.
-
Šimon Kvíčala
commented
Missing support for the new version of REACT 16+ and hence for the new version of Office UI Fabric React seems to be the most problematic
-
Michael Pispers
commented
A better version of the quicklinks webpart would be nice (with (layout)options similar to the SPO version). ...same for the news webpart.
-
Tomasz
commented
You know wahat would be nice:
- Latest version of React,
- Ability to choose version of Typescript
- Latest UI Fafric -
Adam
commented
How about Fabric? In our solution we cannot use newer Fabric components like Shimmer, ShimmeredDetailsList for example. Why? Old dependecies. Also there is no possibility to update React. It feels like OnPremise is abandoned.
-
Anonymous
commented
If i'm understanding Tenant Wide Deployment correctly then it would be nice to have that option. It's tedious to have to delete the web part and add it back for each sub-site I want to use my web-part on.
-
Anonymous
commented
Not OP, but I'd like to see the ability to update the React/Typescript versions.
I understand this can cause challenges, but leaving this alone feels like an abandonment of the on-prem platform.
-
Can you provide more details on what capabilities you'd like to see in the later versions of the SharePoint Framework in the SP2019 platform? Notice that all features which have been released to GA in SPFx since 1.4.1 have cloud dependencies, which will not work in on-premises as for example Graph APIs are not available there.
As we also do not control the server side version of your farm, we cannot update the supportability unless there will be a major SP2019 update for the needed capabilities, but not quite sure what exactly you are looking from the latest versions.
Notice also that we cannot keep the on-premises farm node, TypeScript and React versions up to date as the on-premises farms are not updated as frequently as we would like, which would cause even bigger challenges for developers as there would be different SPFx versions used in SP2019 platform, depending on the installed CU.
We are absolutely looking into different options, but would first need to understand more details on the ask. What features you'd be looking into use in SP2019 platform with the newer SPFx version? Thanks for the details advance.
