feat: support nuxt 3 static rendering

[Lexpeartha]

Types of changes

• New Detector
• Bug fix (a non-breaking change which fixes an issue)
• New feature (a non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Description

Added line that should recognize if current page has been prerendered on nuxt 3. However, I'm not quite sure if prerenderedAt returns value only per route, and if there is a more reliable way to actually detect if whole project has been prerendered.

[atinux]

Would love to have an advice from @danielroe on this

[danielroe]

This looks right to me, at the moment, but we may well need to update as we finish off the rest of nuxt/nuxt#14507.

cc: @pi0

[pi0]

Thanks for PR. LGTM too. prerenderedAt will be always in global NUXT. for pre-rendered pages (unless we renamed it for some reason in the future wich is unlikely).

[Lexpeartha]

Interesting, so in that case maybe detector should prioritize static rendering(or vice versa), in cases where serverRendered is true, if only that route. Still not sure if "Rendering" sections should just display mode for current page (adding prerendering of the page in nitro config) or for the whole project (nuxt generate)

[danielroe]

serverRendered means 'this is not a client-only page' (ie. similar semantics to ssr: true in nuxt config), rather than an alternative to static.