Vite unable to find base tsconfig in a yarn monorepo

[bskinner]

Describe the bug

I'm using a Yarn monorepo for a project, and I have share tsconfig files located in a separate package within the monorepo. When running vite or vite build, vite will be unable to resolve the base configuration and prints the following message (<path-to> is not literally printed, but is a stand-in for the actual path on my filesystem):

[WARNING] Cannot find base config file "/<path-to>/tsconfig-locate-repo/packages/tsconfigs/config" [tsconfig.json]

    tsconfig.json:2:13:
      2 |   "extends": "tsconfigs/config",
        |              ~~~~~~~~~~~~~~~~~~

Both Typescript (tsc) and VSCode are able to successfully resolve the location of the base config, and do not display any warnings or errors about not being able to resolve the config file.

Switching the nodeLinker mode in the .yarnrc.yml file from pnp to node-modules allows for the base config to successfully be found and results in the correct behavior.

Expected Behavior

The path to the base config should be properly resolved, and a warning should not be printed.

Actual Behavior

The base configuration can not be resolved and Vite completes it's operation without including the settings in the extended configuration.

Reproduction

https://github.com/bskinner/tsconfig-locate-repro

Steps to reproduce

Run yarn then run either yarn workspace vite-demo build or yarn workspace vite-demo serve (both will show the warning)

System Info

System:
    OS: Linux 5.15 Ubuntu 22.04.4 LTS 22.04.4 LTS (Jammy Jellyfish)
    CPU: (12) x64 12th Gen Intel(R) Core(TM) i5-1245U
    Memory: 13.54 GB / 15.62 GB
    Container: Yes
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 20.10.0 - /tmp/xfs-1b4eff7a/node
    Yarn: 4.1.1 - /tmp/xfs-1b4eff7a/yarn
    npm: 10.2.3 - ~/.nodenv/versions/20.10.0/bin/npm

Used Package Manager

yarn

Logs

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to vuejs/core instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[sapphi-red]

This seems to be a bug in esbuild: evanw/esbuild#3698

[bskinner]

Thank you for the update!

[sapphi-red]

It was fixed in esbuild 0.20.2 so it will be fixed in Vite 5.2.

[bskinner]

Much appreciated. I checked the example included with my original issue using vite 5.2.0-beta.1 & esbuild 0.20.2 and all looks good.