New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(env): server/public variables #10881
feat(env): server/public variables #10881
Conversation
Co-authored-by: Bjorn Lu <bjornlu.dev@gmail.com> Co-authored-by: Emanuele Stoppa <my.burning@gmail.com>
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we have some test case for output: "hybrid"
with prerendered pages (opt-in and opt-out)?
/** | ||
* @docs | ||
* @description | ||
* Module is only available server-side | ||
*/ | ||
export const EnvServerOnlyModule = { | ||
name: 'EnvServerOnlyModule', | ||
title: 'Module is only available server-side', | ||
message: (name: string) => `The "${name}" module is only available server-side.`, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some thoughts for myself: I know we have a few virtual modules that currently only meant to work in the server-side only. Maybe we can consider making this more generic later. We don't have to change this now.
Changes
Testing
Docs
N/A