Multi-line environment variable not working

[reza-ebrahimi]

Verify canary release

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

Provide environment information

Operating System:
  Platform: linux
  Arch: x64
  Version: #79~20.04.1-Ubuntu SMP Thu Apr 20 22:12:07 UTC 2023
Binaries:
  Node: 20.2.0
  npm: 9.6.6
  Yarn: 1.22.19
  pnpm: N/A
Relevant packages:
  next: 13.4.4
  eslint-config-next: 13.4.4
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 4.9.5

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://codesandbox.io/p/sandbox/adoring-fog-4nkuzo

To Reproduce

• Open sandbox
• Navigate to /env route.
• Check the logs

Describe the Bug

The output of console.log(process.env.GITHUB_PRIVATE_KEY) is "-----BEGIN PRIVATE KEY-----.
If you look at the .env file, only the first line of environment variable is printed into console.

console.log(process.env.GITHUB_PRIVATE_KEY);
// output: "-----BEGIN PRIVATE KEY-----

Note: The private key is invalidated.

Expected Behavior

Printing all lines as it is.

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[joshtinhan]

@reza-ebrahimi this issue will be fixed if PR #38481 got merged.

[balazsorban44]

Correct. We cannot merge it currently, as it would be a breaking change. But you can follow the above-mentioned PR for a resolution.

[reza-ebrahimi]

@balazsorban44 As you said that PR is still not merged, so why this issue is marked as completed then closed?

[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.