-
Notifications
You must be signed in to change notification settings - Fork 27.3k
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
Remove dotenv from all Next.js examples #15225
Comments
Hi, I'd like to tackle that. |
All yours! |
There is something I would like to confirm. I'll remove |
hi @Timer so I just remove the dotenv dependency from all of 5 examples that you point that? |
Well the examples need updated to leverage the new environment support, it's a bit involved! |
@Timer , created a PR for auth0 example ,rest will create PR soon. |
We should remove the dotenv dependency from all Next.js examples (in favor of Next.js environment support): #15225
Remove the dotenv dependency from all examples (in favor of environment support): #15225 All variables are exposed to the client. This Example does not use firebase-admin.
removed the dotenv dependency in favor of Next.js environment support: #15225 The example seems to work with no other changes required ![Screenshot 2020-08-03 at 12 03 22 PM](https://user-images.githubusercontent.com/11258286/89152753-557d6480-d581-11ea-919c-4b89a6bec4b6.png)
We should remove the dotenv dependency from all Next.js examples (in favor of Next.js environment support): vercel#15225
Hi there, it seems |
Address one of the bullet points from #15225 to remove unused dependencies on `dotenv` now that it's supported by default in Next.js.
As far as I can tell, this has been addressed. As of writing, the only reference was in |
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
We should remove the dotenv dependency from all Next.js examples (in favor of Next.js environment support):
The text was updated successfully, but these errors were encountered: