Open nezed opened 3 months ago
Start a new pull request in StackBlitz Codeflow.
The root cause seems to be dotenv-expand@^11.0.3
, brought to Vite@5.1.2 with #15875
See the issue motdotla/dotenv-expand#124
Working on this issue
having the same issue. thanks @akashMasih for working on a solution!
Hey @akashMasih @bitbirddev, don't hesitate to collaborate on root-cause issue motdotla/dotenv-expand#124 as well. Just a thumbs up or a comment would be great :wink:
Describe the bug
We're using env expansion feature for our .env files.
Given following .env file as example:
We expect, the behaviour of Vite@<=5.1.1:
Actual result for Vite@>=5.1.2:
the
-678-ab
part is missing nowReproduction
https://stackblitz.com/edit/vitejs-vite-yalk8f?file=.env
Steps to reproduce
UPD: Seems that the braking change have only affected the env expansion with kebab-cased content after the env var reference.
Example:
Vite@<=5.1.1 (correct)
Vite@>=5.1.2 (breaking change)
You can try it yourself by changing a Vite version in this minimalistic Vite-only example
System Info
Used Package Manager
npm
Logs
No response
Validations