Dominik G.

related in svelte: https://github.com/sveltejs/vite-plugin-svelte/issues/953 i'd rather not hardcode extensions though. given that ts itself does not resolve .vue files with `**/*` , one could argue that configurations targeting custom extensions...

this would affect every user of tsconfck. It's primary use is to read tsconfig files as typescript would. Do you have information on how typescript deals with this? tsconfck isnt...

yes, if the user uses a tsconfig that explicitly has the .vue extension it should work ``` "include": ["src","src/**/*.vue"] ``` The issue at hand seems to be that some tooling...

ahh, thats unfortunate. I think past me added that as an optimization to skip all the regex checks in isIncluded if we can deduce from the extension already. Does it...

a customExtensions option could still be the best compromise here, which leaves users in control. It would require a slight refactoring for the extensions regex group and passing the options...

customExtensions would not be in tsconfig.json but passed to tsconfck as part of the options to parse. It would not depend on the tsconfig file. Another option could be to...

given #199 i have to rethink how globs are implemented and this might start to work when setting `**/*` but pending clarification of how typescript itself treats `src` vs `src/**/*`

please provide a link to a minimal reproduction, not a huge monorepo.

please check #189 and lmk if that works for you. I did add a testcase based on your config so it really should ;) Thanks for the reproduction

fix released in 3.1.2