You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So I guess useDefineForClassFields's value is derived from target and not from compilerOptions.target.
Is this inteded? I think it makes sense whether the value is derived from A or B.
The text was updated successfully, but these errors were encountered:
sapphi-red
changed the title
--target=esnext --tsconfig-raw='{"compilerOptions": { "target": "es2021" }}' will default useDefineForClassFields to true since 0.15.8--target=esnext --tsconfig-raw='{"compilerOptions": { "target": "es2021" }}' will default useDefineForClassFields to trueSep 30, 2022
When transforming the code above with
--target=esnext --tsconfig-raw='{"compilerOptions": { "target": "es2021" }}'
, the output is:This output is the same with the one with
useDefineForClassFields: true
.esbuild repl
So I guess
useDefineForClassFields
's value is derived fromtarget
and not fromcompilerOptions.target
.Is this inteded? I think it makes sense whether the value is derived from A or B.
refs vitejs/vite#10296
The text was updated successfully, but these errors were encountered: