Sp-dev-docs: Porting solution to on-premise

[jonathanhotono]

Category

• [x] Question
• [ ] Typo
• [ ] Bug
• [ ] Additional article idea

I have built a few webparts for some clients that are using O365, however now I got requests to port the react based webparts to on-premise 2013/2016. Is there any solution for me to port this spfx webparts to on premise? I understand that some feature like manifest(properties) and context may not be available, but this can be replaced with something else on-prem?

[waldekmastykarz]

Have you seen this sample: https://github.com/SharePoint/sp-dev-samples/tree/master/Samples/react-generic-app? At this moment it's the only thing available on-premises that you could use, and which reuses some of the concepts of the SPFx. Using this approach you will lose the property pane, so if you require it, you would have to build your own implementation of it.

[jonathanhotono]

Thanks @waldekmastykarz , is this project monitored and supported by MS too? Or we(community) just have to maintain it on our own?

[waldekmastykarz]

It's a community-owned sample that doesn't have a Microsoft SLA if that's what you're asking.

[VesaJuvonen]

I think we have covered the question in the answers. Thx @waldekmastykarz for the replies and @jonathanhotono for the question. Like covered here, SPFx is not yet supported in on-premises. Client-side web parts will be landing to SP2016 with Feature Pack 2 later this year. Provided sample shows how to build customizations using modern web stack also in on-premises. Technique is absolutely supported approach, but the sample itself is provided as a generic sample and maintained by the community.

[jonathanhotono]

Thanks @waldekmastykarz

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues