My situation right now is that i am converting a static site into Nuxt. Which means that instead of converting my static JSON files into HTML files, i am now loading the JSON files asynchronously into my pages and populating them. In other words, SSR is a bit overkill for me, since i am able to render everything as static information. Does it make Nuxt completely useless for me, since i am adding an extra complexity which suddenly requires pre-rendering or SSR? Or is there a way to overcome this hurdle while still having the ability to enjoy the fruits from an SPA experience? One way to get around this issue is running it as a SPA but adding a pre-rendering service on top of it, but this introduces extra cost and delay due to the nature of caching.
This is not exactly an issue, but i guess that many users out there, regardless of they are using Jekyll, Metalsmith, Hexo, Hugo or whatever, are most likely taking the shift towards a SPA at some point and run into this problem.
My tech stack at the moment is DatoCMS -> Metalsmith -> Netlify CDN which i am changing to DatoCMS -> Nuxt -> Netlify CDN, whereas static generation is finding place in the Nuxt setup.
Any input would be great :-)
<!--cmty--><!--cmty_prevent_hook--><div align="right"><sub><em>This question is available on <a href="https://nuxtjs.cmty.io">Nuxt.js</a> community (<a href="https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1728">#c1728</a>)</em></sub></div>