We intentionally do not support skipping dts when going to definition outside of templates, as that somewhat goes beyond Vue’s responsibilities.

You can load TS or ESM files by jiti, we believe that having it built-in will lead to excessive code coupling.

Is the ESM required for your use case?

It's readonly so we should not modify it.

You can access ast by "sfc.scriptSetup.ast". Yeah, I also hope to support ESM as soon as possible. This will take some time.

If you want to avoid manual processing, you can refer to github.com/vue-macros/v...

In the "resolveEmbeddedCode" hook, filter for "embeddedFile" with id starting with "script_", then search for the string "useRoute" in its content and insert some code; you can use the Volar Lab extension to view the final generated virtual code. This should serve as a temporary debugging way!

It's worth mentioning that the main part of transforming Vue code into virtual code is itself a plugin, so I haven't thought of a good way to write plugins for plugins yet; however, we can now use a somewhat hacky way to modify the virtual code after it has been generated. So we can try this:

language-tools/packages/language-core/lib/plugins at master · vuejs/language-tools ⚡ High-performance Vue language tooling based-on Volar.js - vuejs/language-tools

Yes, you can refer to the specific way of writing plugins at github.com/vuejs/langua....

Just use it like this in tsconfig.json:

I think we could introduce a hook that extends composables' types (Just like `useTemplateRef` but customizable)