I'll test with npm run dev next time it occurs to see if it's uniquely a bun issue

Notices with pnpm as well

@jhwz @xmlking have any of you guys figured out how to reproduce this? It happens all the time for me but it's random, usually after updating a dependency

Not using bun, but I'm running into this same error message- What repo structure do you have? I'm using a monorepo with per-package tsconfig.json configs, and can reproduce the issue by creating a root-level tsconfig.json. Once I do that, esbuild starts hanging and blocking the vite build. Haven't found a workaround yet.

Things were fine, but in one of the recent typescript-eslint updates, it started throwing errors unless there was a root-level tsconfig.json, so I'm stuck between a rock and a hard place.

Currently using:

• Yarn 4.3.1 w/ pnp
• vite 5.4.3
• Typescript 5.5.4
• eslint 9.10
• typescript-eslint 8.5.0 (typescript-eslint/parser is at the same version)

I managed to find a workaround and traced the issue in my configuration. esbuild seems to hang when extending tsconfigs from a local package (this may also impact extending from external packages, but I haven't tested it).

My structure of the root tsconfig.json is arranged as:

flowchart LR
 subgraph tsconfig-shared
 base -->|extends: ./base| node
 end
 node -->|extends: tsconfig-shared/node| root-tsc["/tsconfig.json"]

Removing the extends from the root tsconfig.json resolves the hang issue and allows the build to continue as normal without issue.

I managed to find a workaround and traced the issue in my configuration. esbuild seems to hang when extending tsconfigs from a local package (this may also impact extending from external packages, but I haven't tested it).

My structure of the root tsconfig.json is arranged as:

flowchart LR
 subgraph tsconfig-shared
 base -->|extends: ./base| node
 end
 node -->|extends: tsconfig-shared/node| root-tsc["/tsconfig.json"]

Loading

Removing the extends from the root tsconfig.json resolves the hang issue and allows the build to continue as normal without issue.

This actually fixed it for me, I moved the config I was extending from svelte-kit into my main tsconfig and all seems well now!

You need to rm -rf node_modules or install with force clear cache options. I think this is due to Bun and pnpm's folder linking

bun i --force should also work. Yes, this is very annoying until the issue gets fixed...

tysm!

Adapter bun? Is it a problem if I use adapter vercel?

Adapter bun? Is it a problem if I use adapter vercel?

I'm not Bun or Vite contributor but I believe the fix was introduced in Bun somewhere between 1.1.30 and 1.1.34

Sorry I don't have much time to test exactly what and where and how was fixed, I just providede the versions that does not seem to trigger that issue anymore.

I doubt that the fix was in svelte-adapter-bun since we're using different adapters and had same issue, I believe bun's adapter did not cause this issue in the first place

Yep, I can confirm it started happening again, though I remember I fixed it and even agter installing new packages I was able to start the server

I can confirm this is happening to me as well with Bun version 1.1.34 on my Mac.

Still happening on macOS

It comes an goes with each version, definitely a regression testing issue

Yes, this keeps on coming back between version upgrades.
Its 'not great.

Even more annoying if the docker build process hangs because somehow vite build does not signal completion.
that's when we start without a node_modules folder.

I just now always do- bun install -f