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] accept PUBLIC as prefix for environment variables #2355
Conversation
🦋 Changeset detectedLatest commit: 6ef28e2 The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
1e51489
to
1f7763a
Compare
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.
At least PUBLIC_
makes it clear that it's public.
I think the changelog should make it more clear that this is a breaking change and how to fix it. |
It's not breaking in that we also still support VITE_. However it is breaking in that if I had an env var called PUBLIC_DATABASE_PASSWORD which was previously a private env var, it is now exposed. It's a super edge case but it could happen. It doesn't feel like a patch version. |
Everything's a patch version in |
Oh hah, yes it is :) |
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.
Looks great and can be extended with exposing it through the settings at a later point.
Commented on #2308 (comment) — tl;dr I feel like this maybe makes things more complicated? |
Closes #2308