>package the client and pull the content dynamically with JS

Please don't do this. Most pages are documents, not interactive web apps.

This bugs the crap out of me when the online documentation for a language/framework/program refuses to render without JS. It's completely unnecessary.

Upvoting this is just not enough. This is the worst aspect of the web currently. Even NASA.gov is just a blank black page without JS enabled.

It's completely unecessary and sacrifices accessibility for ease of development.

Sometimes is not even about ease of development, but just a following of trends without thinking. SPAs are a bad choice for content-based sites for several reasons.

People often ask the wrong question: "which JS framework should I use?" (wrong first question) instead of "should I build a site that requires users to execute JS?"