Go To Definition and Other Intellisense powered functions are borked

[mlevison]

Since this doesn't appear to be widely reported I will assume it is me problem. Please tell me setting I got wrong.

This GIF is an attempt to illustrate what I see

Plugin version: 1.8.14
VSCode 1.99.3
MacOS 15.4.1

[remcohaszing]

It’s neither a you problem, nor an MDX problem. It’s an Astro problem. The Astro language tooling uses a language server for its TypeScript integration instead of a TypeScript plugin. As a result, it can’t be combined with other languages such as MDX.

I don’t know the current state or plans to resolve this on the Astro side. Maybe @Princesseuh knows.

[Princesseuh]

Unfortunately I have no time to give to the Astro language-tools nowadays, so I don't think this will change soon.

[mlevison]

Thanks to both of you. Curiously up until Easter Monday (+/- a few days), it worked.

[remcohaszing]

It’s ambiguous what you are referring to with “it”. I did create a new release of the MDX VSCode extension April 19th. I can’t tell what’s going on without a minimal reproduction. That includes:

• A minimal repository where the issue occurs. This includes:
  • VSCode settings
  • tsconfig.json
  • An MDX file
  • Presumably an Astro file?
• The minimal set of extensions with which the problem occurs
• Exact steps to reproduce the issue
• A description of the old behaviour, which you are expecting
• A description of the new behaviour

[Princesseuh]

FWIW, while the Astro language server doesn't use a TS plugin, we do have one which I would believe could somewhat allow this to work? https://github.com/withastro/language-tools/tree/main/packages/ts-plugin

[mlevison]

@remcohaszing I genuinely don't know if I'm trying to report a bug. I appreciate the repo, steps. I will reach out to a few other people before I go further.