Hybrid rendering stage 3 proposal

[matthewp]

Summary

Provide a output: 'hybrid' mode to allow static sites to opt-in certain pages to be dynamic (not prerendered).

Links

• Full rendered proposal
• Stage 2 proposal
• Stage 1 proposal

[jamesli2021]

As opposite to 'server', using 'hybrid' is confusing, I prefer 'defaultstatic' or 'defaultprerender' as it's more meaningful in the docs.

[matthewp]

This has been out as experimental since 2.5. I'm moving to have this RFC merged in and experimental label removed. We'll now enter the final comment period. If anyone has issue with this RFC being merged please voice now, thanks!

[zadeviggers]

Again, I'm still mainly in favor of not introducing a "hybrid" option, and instead going for an object configuration. But I can see how this way is simpler for the user, if less future-proof and more confusing, so I don't feel too strongly either way.

[matthewp]

@zadeviggers Did I miss this idea? Could you link to it? The object configuration I mean.

[zadeviggers]

@matthewp here are the relevant comments:
#539 (comment)
#539 (comment)

[matthewp]

Ah yeah. I see what you mean. Personally I would keep output as a string and then have a separate option for the default:

output: 'server',
build: {
  prerenderDefault: false
}

I think there's still some perception problem with this approach where people see the default being false as being the wrong choice.

I think we should proceed with the current 'hybrid' option for now. 3.0 is coming up so we can still make this better in the future. Since this is mostly about bikeshedding the config name and not how exactly it works. Sound fair?

[matthewp]

We're going to go with this approach for now. Happy to continue refining it as we approach 3.0.

[zadeviggers]

Awesome, that sounds good.