> Examples being history management and back button, state management (especially if you prefer immutability), and server side rendering. Maybe/maybe not, I us

> Examples being history management and back button, state management (especially if you prefer immutability), and server side rendering. Maybe/maybe not, I use a Mini-SPA approach where I pass down libraries.js, bundle.js and foo-page.js (all minimised and such) on the initial page load I pull the data and pass that down as well (avoiding the round trip). With that approach I get most of the benefits of an SPA in terms of behaviour but without having to use client side history management and I don't break the back button. I still get to issue calls and such and the actual orchestration of the page side js is done with a very light class that each page extends from that has just a handful of methods. Component orchestration is managed with pub/sub. I've found it an extremely nice way to develop, there isn't a massive duplication of code and it's very easy to reason about, it lacks a few of the benefits of a pure SPA but has most of them and the separation is very easy.