Multiline environment variables dont work as expected

[nuntax]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 18.17.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant Packages:
      next: 13.4.13-canary.2
      eslint-config-next: 13.4.12
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A

Which area(s) of Next.js are affected? (leave empty if unsure)

No response

Link to the code that reproduces this issue or a replay of the bug

https://github.com/nuntax/next-js-bugreport

To Reproduce

Have a multiline environment variable like a ecdsa key for JWT usage.
.env.local:

PUBLIC_KEY='-----BEGIN PUBLIC KEY-----
multi-line
-----END PUBLIC KEY-----'

When now logging the environment variable:
console.log(process.env.PUBLIC_KEY)
The console output looks like the following:
'-----BEGIN PUBLIC KEY-----

Describe the Bug

Only the first line of the environment variable is getting loaded.
Weirdly enough adding the experimental --turbo flag to next dev resolves the issue.

Expected Behavior

The expected behaviour is that the entire variable is loaded and that
console.log(process.env.PUBLIC_KEY)
prints

PUBLIC_KEY='-----BEGIN PUBLIC KEY-----
multi-line
-----END PUBLIC KEY-----'

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[balazsorban44]

This is currently not possible, as it would be a breaking change to update dotenv.

You can follow this PR: #38481 (comment)

[nuntax]

For anyone looking for a workaround, just replace the line breaks with \n.

[github-actions]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.