Inject storybook environment variables #105
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #104.
This injects storybook environment variables through the
define
config of vite, similar to what the webpack builder does using theDefinePlugin
. I needed to create a customized version of one of the core storybook functions, since it assumes thatprocess.env
is going to be used, whereas with vite we useimport.meta.env
.I also added example stories in react, vue, and svelte (my first time writing vue and svelte!). They're ugly, but they show that the STORYBOOK environment variable is being provided correctly (it wasn't previously).
Before:
After: