You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I know Issue #222 dealt with this to some degree, but I'm still seeing issues around the management of keys in .env files and Stripe complaining about it with the error in the title.
In our setup, we have various .env files for different build processes. Since we're using Vite for the build, it supports the naming of env files per environment, such as:
.env.local .env.development .env.staging
in addition to standard .env files. Yet I still get the errors on any .env file other than .env and .env.local.
Any chance you can expand the linter rules to ignore any file starting with the name .env?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi there-
I know Issue #222 dealt with this to some degree, but I'm still seeing issues around the management of keys in .env files and Stripe complaining about it with the error in the title.
In our setup, we have various .env files for different build processes. Since we're using Vite for the build, it supports the naming of env files per environment, such as:
.env.local
.env.development
.env.staging
in addition to standard
.env
files. Yet I still get the errors on any .env file other than.env
and.env.local
.Any chance you can expand the linter rules to ignore any file starting with the name
.env
?Thanks!
The text was updated successfully, but these errors were encountered: