Forum Discussion
Sharepoint 2016 On-Premise SPFx Alternatives
(1) PnP is your best resource here....even you will see a lot of SPFx stuff, you can potentially re-use the code there
(2) No, you will have to start from scracth while as I said in (1) you can potentially re-use code
It was not my decision the architects are the leads on our development team and they made the decision. I am not even certain I can use PnP. The architects don't want to install anything on the farm with the exception being farm solutions.
I'd be asking your architects what they define as "installing" something (as a Consultant I've made a career of challenging everything and frequently being told to wind my neck in). All modern development now takes place with client side code, so there's nothing that they need to install beyond the actual SharePoint 2016 supported updates. The SPFx elements themselves get deployed through the app catalogue, in the same way as Add-ins so if you're looking to do any type of portable development for SharePoint you're going to be adding items there. If you are able to persuade your architects, then jcgonzalezmartin is correct in pointing out that PnP will be your number 1 resource.
Is your Farm configured to support the Add-in model? If so you could explore SharePoint Hosted Add-ins or Provider Hosted Add-ins as they were the recommended way of developing for SharePoint 2013+.
If you still encounter resistance to that approach, you've always got Script Editor Web Parts which allow you to embed and reference JavaScript directly on the page.
- Totally agree here...additionally, they should consider to use in each case best option and SPFx to me is better to build WebParts than using classic WebParts. Also I don't know if you have in mind to move to SP 2019 at some point or even to SPO, in the later case the more you use the development patterns recommended by Microsoft, the less painfull a migration in the future will be
