If you're curious about the frontend path I took, it was roughly:
* jQuery with no framework
* Backbone (for a couple years)
* Backbone + Marionette (for a couple more years)
* Angular (for about a week)
* React (for the past few years)
What do you think of Vue.js?
State management with React is another story; I've used Reflux and Redux a lot, and am experimenting with Mobx now.
I'm using stuff like slickgrid[0], jquery-ui datepicker, json-editor[1] and wonder how I will drive these components from something like Angular or React?
doh, quickly googled for the github links below and saw there now a slickgrid-es6[2] fork which I have not tried. But my question still stand: how do you drive jquery libs from newer frameworks?
[0]: https://github.com/6pac/SlickGrid/wiki
Maybe it's frowned upon but I don't really like to use those (usually partial) Bootstrap re-implementation, especially in non-SPAs where you already have jQuery and/or Bootstrap.
Of course it's becoming less and less necessary.
On component mount/unmount, you can apply a jQuery library to the DOM node and optionally clean it up.
It's the same way you can wrap a <canvas> node with a React component and otherwise do all your draws outside of React (like for a game). This way the node is still integrated into your React app but React does nothing more than create/remove it.
Once you've wrapped it in a component, you can more or less drop that component anywhere in your view hierarchy and not have to think about the fact that it's using jQuery under the hood.
This highlights one of my favorite things about React and similar frameworks, which is that it's the closest thing to actual, useful encapsulation of components I've seen in a frontend framework. It's not perfect, but it's much better than everything I used before it.
I wrote it for my own convenience but others may find it useful.
If any other site tries to POST to the API on behalf of the current user they'll get a "Authentication credentials required" message.
If you don't need JWT (I'd probably leave it out next time round) then Django Rest Framework comes with a simpler bearer token auth class (among others): http://www.django-rest-framework.org/api-guide/authenticatio....
edit to add - if you're asking specifically about sharing sessions between the JS app and the Django server-side form, I believe this is what you're looking for:http://www.django-rest-framework.org/api-guide/authenticatio..., i.e. you'll still need to pass the csrf token into the JS app.