Support static deployments with `ssr: false`

Disabling SSR limits the ability to prefetch query endpoints in the generation process and therefore generated website will not contain any content.

There are some approaches we can take to support non-ssr websites:

• We can ship nitro into service workers to handle API requests for content APIs and provides content live in production.

• Like Content v1 we can expose the whole database to the client using /api/_content/cache API (pre-rendered) and search and provide content live in the client.

\cc @pi0 @Atinux @Tahul

[jshimkoski]

First things first, I want to thank the Nuxt Content team for all of your hard work. You all are amazing developers.

That said, I’ve run into this issue as well.

Being able to generate a static distribution of a Nuxt Content v2 site is crucial functionality and the ability to do this was a huge selling point of v1.

Requiring a Nodejs server in order to run a Nuxt Content v2 site is not only crippling, but it makes the development vs production flow a nightmare.

For example, I have a fully functional (in development) version of an application rewritten for Nuxt Content v2 but it cannot be deployed in the same manner as its v1 counterpart because it blows up with a “You should use slots with <ContentRenderer>” error after running npm run generate and npm run preview then visiting it in a browser.

For users without access to a Nodejs server, a static hosting solution is vital. I was actually shocked that this functionality wasn’t baked into the stable release (especially after migrating everything over to v2, just to find out later that SSG doesn’t currently work).

I hoping this issue can be resolved in the near future.

Thanks!

[farnabaz]

Since the Service Worker presets work as expected, we need to

• Update documentation, and add notes about SPAs. There are two options,
  • Use Nitro’s Service Worker preset
  • Pre-render pages and create a static website
• Detect ssr: false warn user and point to docs