You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After updating from 10.0.7 to 10.0.8next.config.js and files imported from it stopped seeing ENV variables defined in .env files. In production mode it still works correctly.
After downgrading to 10.0.7 it works again.
Expected Behavior
Ir reads .env files content.
To Reproduce
Add VARIABLE_NAME=123 to .env file.
Add console.log(process.env.VARIABLE_NAME) to next.config.js.
Run yarn next dev in CLI.
Check CLI output for a line with 123.
On 10.0.8 it return undefined, on 10.0.7 it returns 123.
The text was updated successfully, but these errors were encountered:
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.
vercel
locked as resolved and limited conversation to collaborators
Jan 28, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Next.js are you using?
10.0.8
What version of Node.js are you using?
15.8.0
What browser are you using?
CLI
What operating system are you using?
macOS
How are you deploying your application?
local
Describe the Bug
After updating from
10.0.7
to10.0.8
next.config.js
and files imported from it stopped seeing ENV variables defined in.env
files. In production mode it still works correctly.After downgrading to
10.0.7
it works again.Expected Behavior
Ir reads
.env
files content.To Reproduce
VARIABLE_NAME=123
to.env
file.console.log(process.env.VARIABLE_NAME)
tonext.config.js
.yarn next dev
in CLI.123
.On
10.0.8
it returnundefined
, on10.0.7
it returns123
.The text was updated successfully, but these errors were encountered: