Lyu, Wei-Da

From my understanding composite is required in project reference. Though yeah, it is mostly related to how `tsc -b` build and vite might not have the same constraint. But this...

@alexlafroscia. Yes, this is the intended behaviour. In svelte-check, there is no check for project assignments; it's the opposite. You pass in the config path, and svelte-check loads the file...

svelte-check behaves like `tsc` without the `-b` flag. Whatever the config is passed in, we load the files included with "the config" and nothing else. If we want to support...

For TypeScript, each tsconfig is its own project. The solution project is no exception. i.e. The files in the referenced project don't belong to the solution project. In `tsc` without...

> It would be handy to have a separate tsconfig for server side code, with different lib entries, where browser APIs are unavailable. As mentioned before. You can use a...

There isn't a config for it, and TypeScript provides this, so we have no control over it. You'll need to use "go to definition" to see how the props are...

I don't think the correct fix. `tsc` does check `ts` files in the node_modules so the inconsistency might come from another place. Please create an issue first with a reproduction...

It might be possible. Since slot props are replaced by snippets and the event is replaced by callback props so there's less inferred type. I tried and the prototype seems...

The issue is about the $lib alias not being recognized in the editor. I am not sure what you meant by "works anyway". The issue is that the VSCode extension/language-server...

I didn't see the package.json with exportMap. Maybe it's ignored because of gitignore? About `.d.svelte.ts `, this isn't exclusive to export maps import. TypeScript would also try this with relative...