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

[@sentry/nextjs] Custom .env file #3683

Closed
samchouse opened this issue Jun 15, 2021 · 3 comments · Fixed by #3786
Closed

[@sentry/nextjs] Custom .env file #3683

samchouse opened this issue Jun 15, 2021 · 3 comments · Fixed by #3786
Labels
Package: nextjs Issues related to the Sentry Nextjs SDK Type: Improvement

Comments

@samchouse
Copy link

Sentry SDK is currently looking for a .env.local file but I have a .env file. Is there a way to have it look for the .env file instead?

@lobsterkatie
Copy link
Member

Currently, no, but it's something we'd consider. Does next load env variables from .env the same way it does .env.local, or do you do that yourself? (That's why we used .env.local.)

@samchouse
Copy link
Author

Nextjs does load from the .env without any change.

19416d8

@lobsterkatie
Copy link
Member

lobsterkatie commented Jul 9, 2021

Hi, @Xenfo. We've changed our approach, so once #3786 is released, this won't be an issue anymore, since we'll no longer be using an env file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Package: nextjs Issues related to the Sentry Nextjs SDK Type: Improvement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants