Replies: 1 comment
-
|
It's because plugin-legacy decides whether to use legacy chunk or modern chunk based on syntax features (ESM, dynamic import, import.meta, async generator) and that differs from the modern target Vite core defines. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Why do Vite and Legacy have different definitions of modern?
Beta Was this translation helpful? Give feedback.
All reactions