tsconfig useDefineForClassFields setting not respected

[molszews]

Describe the bug

My project requires use of setting useDefineForClassFields: true in tsconfig.json. For some reason the output presented by npm run dev behaves like that setting was set to false.

Reproduction

Create from React-TypeScript template (npm init @vitejs/app my-app -- --template react-ts) and add following code to App.tsx

class ContactInfoDto {
    firstName; lastName;
}

and inside App():

const contactInfo = new ContactInfoDto();
Object.keys(contactInfo).forEach(k => console.log(k));

It should console.log two lines when useDefineForClassFields set to true in tsconfig.json. (It works that way executed under webpack+babel or webpack+esbuild)

System Info

Output of npx envinfo --system --npmPackages vite,@vitejs/plugin-vue --binaries --browsers:

npx: installed 1 in 0.738s

  System:
    OS: Linux 5.4 elementary OS 5.1.7 Hera
    CPU: (12) x64 Intel(R) Core(TM) i7-8850H CPU @ 2.60GHz
    Memory: 4.45 GB / 31.16 GB
    Container: Yes
    Shell: 4.4.20 - /bin/bash
  Binaries:
    Node: 12.21.0 - ~/.nvm/versions/node/v12.21.0/bin/node
    Yarn: 1.22.10 - /usr/bin/yarn
    npm: 6.14.11 - ~/.nvm/versions/node/v12.21.0/bin/npm
  Browsers:
    Chrome: 90.0.4430.85
    Firefox: 87.0
  npmPackages:
    vite: ^2.2.3 => 2.2.3 

Used package manager: npm

[Obiwarn]

Same here. This also seems to break some MobX functionality .

[haoqunjiang]

According to ESBuild documentation, the transform API does not access the file system, so it can't automatically discover the tsconfig.json. Vite needs to pass the tsconfigRaw option explicitly to it.

[haoqunjiang]

On the other hand, I think this API design in ESBuild is quite confusing.

Why does it accept a path string in the sourcefile option but still refuse to access other part of the file system to get the corresponding tsconfig.json?

[haoqunjiang]

A note: in TypeScript 4.3, target: 'esnext' now indicates useDefineForClassFields: true.
microsoft/TypeScript#42663