Go to definition in a Vue SFC file on the import of another Vue component in a library with declaration maps doesn't work

[segevfiner]

1. Clone https://github.com/segevfiner/volar-declaration-map-issue
2. pnpm i
3. pnpm -r build
4. Open the project in VS Code.
5. Open "packages/bar/src/App.vue", and click on HelloWorld in the import on line 3 and go to definition, it goes to the built .d.ts file of HelloWorld.vue.
6. Open "packages/bar/src/main.ts", and click on HelloWorld in the import on line 8 and go to definition, it goes to the HelloWorld.vue source file.

This seems to happen in both non-takeover and takeover mode.

Related to the previously closed #1344

[so1ve]

@segevfiner I think this is expected - when importing from foo, you are bundling foo first, then bundle bar, so you are not importing its source, but the build result.

If you want to goto HelloWorld.vue, I suggest you use this: https://www.typescriptlang.org/tsconfig/paths.html

[so1ve]

Ah - wait, declaration maps?

[Ping-Gao]

I am having this issue as well, declaration maps only worked in ts file but not in vue file.

[Ping-Gao]

Ah - wait, declaration maps?

He was talking about this https://www.typescriptlang.org/tsconfig#declarationMap We want to go to source code rather than .d.ts.

[max-220]

I noticed that it is caused by an incorrect source file name with .ts extension in e.g. SomeComponent.vue.d.ts.map

It's still reproducible with "vue-tsc": "1.8.27":

{
  "version":3,
  "file": "SomeComponent.vue.d.ts",
  "sourceRoot": "",
  "sources":["../../../../src/components/SomeComponent.vue.ts"], 
                                                          ^^^^
  ...
}
                                                                            

And with "vue-tsc": "2.0.6" it works as expected:

{
  "version":3,
  "file": "SomeComponent.vue.d.ts",
  "sourceRoot": "",
  "sources":["../../../../src/components/SomeComponent.vue"], 
  ...
}