fix: import.meta.env and process.env undefined variable replacement (fix #8663) #10958
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fixes Vite using the replacement for "import.meta.env" instead of the replacement for "import.meta.env." when replacing an undefined environment variable (and any other "."-ending replacement never being used)
fix #8663
Additional context
Code:
import.meta.env.UNDEFINED
Expected replacement:
({}).UNDEFINED
Actual replacement:
{"BASE_URL":"/","MODE":"production","DEV":false,"PROD":true}.UNDEFINED
Note that the above is inlining the full list of known env variables but also creating invalid JavaScript in some scenarios.
Issue originally reported at #8663
Additional broken build repro:
https://stackblitz.com/edit/vitejs-vite-bthpb6?file=main.js&terminal=build
What is the purpose of this pull request?
Before submitting the PR, please make sure you do the following
fixes #123
).