Skip to content
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

This Stripe API Key is hardcoded. For better security, consider using a .env file. See https://stripe.com/docs/keys#safe-keys for more advice #622

Open
amcjen opened this issue Jul 15, 2022 · 0 comments

Comments

@amcjen
Copy link

amcjen commented Jul 15, 2022

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant