TypeScript paths

[Rich-Harris]

Per #75 (comment):

TypeScript isn't resolving aliases like $components/Blah.svelte and $app/stores, and I don't know how to coax it into doing so. This didn't work:

"compilerOptions": {
  // ...
  "baseUrl": ".",
  "paths": {
    "$components/*": ["./src/components/*"],
    "$app/*": [".svelte/main/runtime/*"]
  }
},

[ehrencrona]

Moving my comment from #75:

The paths setting seems to make VSCode resolve to the right source file for me. On the other hand I don't get an error if the source file is missing (line below).

I suspect the error you get is because for whatever reason you don't have these typings that I have in .vscode/extensions/svelte.svelte-vscode-102.3.0/node_modules/svelte2tsx/svelte-shims.d.ts

declare module '*.svelte' {
    export default Svelte2TsxComponent
}

declare class Svelte2TsxComponent<
    Props extends {} = {},
    Events extends {} = {},
    Slots extends {} = {}
> {
    $$prop_def: Props;

[dummdidumm]

You don't get an error for $xyyy/Van.svelte because of the ambient module declaration: declare module "*.svelte" means "anything ending with .svelte is a known module". That is needed for TS-files to not error on Svelte imports, but at the same time it silences real errors in Svelte files. Honestly I'm not sure how to work around this. The only thing that comes to my mind is to have some kind of defined d.ts file with a special name which will not be loaded by the Svelte extension - not sure if that will work though; and even if it does, we would need to remove that ambient definition from the Svelte core types, too.
Vue with Vetur has the same problem btw.

[dummdidumm]

I cannot reproduce this (never could, actually) so I'm closing this. Feel free to reopen if the paths thing still does not work for you.

Regarding the "incorrect Svelte paths do not error" - this is a different thing for me not related to this issue.