Jean-Noël

Same problem. Whereas it works with Node.js. FYI, as it's difficult to know the responsible between `bun` and `vue-tsc` (or `vite` ?), let's add a cross-reference: https://github.com/vuejs/language-tools/issues/4082

> Not sure why but you can fix this by adding .d.ts file in project src > > //vue-shim.d.ts `declare module "*.vue" { import type { DefineComponent } from "vue";...

@rukshn > > Not sure why but you can fix this by adding .d.ts file in project src > > //vue-shim.d.ts `declare module "*.vue" { import type { DefineComponent }...

Same issue, and by the way the folder "dist" is staying empty although there's no error.

> You can roll back Vue - Official version to 1.8.27 Actually, VSCode and extensions should not be concerned : I should be able to use `vue-tsc` command independently (on...

> Does other package manager / runtime, such as npm and node.js, have the same error? No, it doesn't! Which is very surprising! `Bun` _might_ be identified as the responsible.

@nethriis > I have the same error on node.js [This example](https://stackblitz.com/edit/vitejs-vite-c2jqqb?file=src%2FApp.vue) works fine with Node.js / Vue.js / Vite. Use: `npm run type-check` to detect my introduced errors in `App.vue`...

[Suggestion from here](https://github.com/oven-sh/bun/issues/4754#issuecomment-2011949253): > Most likely the linked issue means that overriding readFileSync as a way to hook into module loading. We do not support that currently. > We do...

Same problem with bless==0.2.6 version 😞

My Solution : Think to **activate** the Bluetooth on Windows :  And I suppose you need to be admin on your machine.