Skip to content

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

@amcjen

Description

@amcjen

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions