Skip to content

Add Support for More .env Files #3226

@laugharn

Description

@laugharn

Problem

I primarily use Prisma with Next.js, and since Next 9.4 they've implemented automatic .env detection, based on Create React App's pattern: https://create-react-app.dev/docs/adding-custom-environment-variables/#what-other-env-files-can-be-used

When doing local development, my DATABASE_URL variable is kept in .env.local, which isn't found by default when I run prisma generate so Prisma commands tend to require some overhead/repetition in my repo.

Suggested solution

Support for the additional .env files used by the popular JS meta frameworks.

Alternatives

A set of local development-specific Prisma commands using dotenv-cli

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions