Forum Discussion
SPFX supported version for SPSE
Hi Int_A1730, what capabilities in the newer SharePoint Framework versions are you interested in and why do you think they would be important to add to SharePoint Server Subscription Edition? I ask because we have many good ideas for additional improvements we could make to SharePoint Server Subscription Edition from customers, so hearing specifically what you're interested in and why will help us as we prioritize what we focus on.
- NicolaeNov 18, 2021Brass ContributorAre you seriously asking this question? See all these beautiful webparts here:
https://github.com/pnp/sp-dev-fx-webparts/tree/main/samples
We can't use most of them and if we can, it's after a lot of work or by using an old/buggy version. At least upgrade the TS and React version if nothing else.
This should be top priority, especially since the modern interface has less than 20% of the functionality of the classic one. - Int_A1730Nov 12, 2021Copper Contributor
1) Tenant wide extensions deployment. We have to do powershell workaround for that or manually upload/uninstall it everywhere.
2) React, Fluent UI, TS versions bump. There are workarounds (https://spblog.net/post/2019/08/08/build-sharepoint-framework-solutions-for-on-premises-sharepoint-with-any-version-of-react-typescript-or-office-ui-fabric-react) but it makes solution unnecessarily complicated. PnPjs is popular lib and currently we have to do workaround to install it https://pnp.github.io/pnpjs/SPFx-on-premises/. I don't expect latest and greatest versions, I understand that onprem is always behind.
- TroyStarrNov 12, 2021
Microsoft
Thanks Int_A1730, this is great feedback and I appreciate the explanation of why you're looking for newer versions of SharePoint Framework. We'll think about this as we plan our future investments in SharePoint Server Subscription Edition.
- sharepointWoesDec 15, 2021Copper Contributor
I am really surprised that anyone needs to be asked why they would want to use a newer version of SPFx. The question should be why not? Cloud dependencies and whatnot is not a valid excuse. Many organisations will continue to use on prem option for the foreseeable future and are being severely handicapped when it comes to development. I am a developer in one such organisation and am constantly disappointed by how poorly thought out SP19 was and am even more disappointed that a product you are releasing 3 years later uses exactly the same SPFx version. From a developer perspective SP SE is basically SP19 on subscription.
I think any developer worth their salt can be trusted to work out what they can and can't do with the newer versions on SPFx within an on prem environment, so give us the flexibility please!