Environment variables no longer passed to app in 9.5 ("ReferenceError: process is not defined")

Bug report

Describe the bug

Process object used to access environment variables in node is missing after upgrading to 9.5.

To Reproduce

Upgraded to nextjs 9.5 and the snippet in the screenshot broke. If I start the app using a command like this NEXT_PUBLIC_LOCAL_FUNCTIONS_PORT=5001 next it works, but if I leave out the environment in the command (i.e. next) it fails.

Tried creating a fresh next app (on 9.5) and was NOT ABLE to reproduce. Might be something with my dependencies.

Expected behavior

I expected that env variables would be able to be looked up on the client.

Screenshots

System information

• OS: macOS
• Browser: Chrome 84.0.4147.89
• Version of Next.js: 9.5
• Version of Node.js: 10.20.1

[Ymirke]

@7iomka it is not possible to use destructuring with process.env in next.js. Line 17 is an error, but you can still define them one by one and it should work.

export const BACKEND_URI = process.env.BACKENDURI
// ...
// ...

Explaination about why is here: https://github.com/vercel/next.js/issues/6888. It is because of a webpack plugin.

[berakoc]

@7iomka it is not possible to use destructuring with process.env in next.js. Line 17 is an error, but you can still define them one by one and it should work.

export const BACKEND_URI = process.env.BACKENDURI
// ...
// ...

Explaination about why is here: #6888. It is because of a webpack plugin.

Destructuring env variables caused process is not defined error. By exporting them one by one, my app is working just fine. Thank you so much!