fix(env): compatible with env variables ended with unescaped $

[sun0day]

Description

fix #12006

.env:

VITE_EXPAND_A=$EXPAND
VITE_EXPAND_B=$DEPEND_ENV
VITE_ESCAPE_A=escape\$
VITE_ESCAPE_B=escape$
IRRELEVANT_ENV=$DEPEND_ENV
IRRELEVANT_ESCAPE_ENV=irrelevant$
DEPEND_ENV=depend

after parsing .env, you will get

env = {
  VITE_EXPAND_A: 'expand',
  VITE_EXPAND_B: 'depend',
  VITE_ESCAPE_A: 'escape$',
  VITE_ESCAPE_B: 'escape$'
}

Irrelevant env variables and VITE_ env variables won't impact each other.

Additional context

---

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Before submitting the PR, please make sure you do the following

• Read the Contributing Guidelines.
• Read the Pull Request Guidelines and follow the PR Title Convention.
• Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
• Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
• Ideally, include relevant tests that fail without this PR but pass with it.

[bluwy]

IIUC this PR would allow trailing $ for any env var, which isn't exactly the same proposed changes from #12006 (comment), but thinking about it more, I think this is indeed the best solution forward without deviating too much from dotenv-expand.

Looks like there's a merge conflict, but the changes looks good to me.

[sun0day]

IIUC this PR would allow trailing $ for any env var, which isn't exactly the same proposed changes from #12006 (comment), but thinking about it more, I think this is indeed the best solution forward without deviating too much from dotenv-expand.

Looks like there's a merge conflict, but the changes looks good to me.

Yeah. It's a bit of a compromise, but I think it's the best solution by far. And it makes sense to leave the trailing $ as it is.