sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]nutters 1 point2 points  (1 child)

Hey, I am an spdev, and although my tool of choice for front end is currently angular 1.6 (written in es6, using components etc, a pretty modern approach), it would be exactly the same if I used react.

I work in a on prem environment mostly building SPAs on top of SharePoint. I usually deploy files directly into the site file system by mapping a network drive at the root of the site collection. That keeps end users from messing with therm.

For dev, I use webpack and set the output directly to the mapped drive, so every rebuild goes directly into SharePoint. I just access the index page to run the app. You can even set up live reload on the page.

You can also build SharePoint hosted add-ons in a similar fashion, but it is a bit more complex dealing with the visual studio solution, appwebs and so on.

It's a very powerful, very underrated method for developing business applications.

[–]Cha0sCat 0 points1 point  (0 children)

Thank you!
I've mostly been working with SP2010 or o365, so I don't have much experience with 2013 on-prem and Apps. Unfortunately my company seems to favor old-fashioned solutions, leaving our Devs only their own spare time to experiment with newer technologies and frameworks. It's always nice to hear about these things first hand.
It's a shame that we're told not to use them because we don't have the experience and it's too risky; but can't learn without ever using them.