what's the mdx language server status by far?

[HomyeeKing]

I intend to write tsx code block at .mdx and I need to get IntelliSense while using some components

// comp.tsx
export default ({title}:{title:string})=><div>{title}</div>

import Comp from './comp' 

// will remind me to add title prop
<Comp  />

I've installed vscode-mdx extension and enable mdx.experimentalLanguageServer, noting happens

[remcohaszing]

I tried your code and it works for me. When hovering over Comp in either the import or the JSX element, it shows hover information. Is this not the case for you? What did you expect to happen?

---

To answer the more generic question in the title: The status is that the language server works quite well IMO, but new issues are still surfacing, so I prefer to keep it behing a flag. Also the language server hasn’t been released to npm yet, so this experience is still only available in VSCode. I’m also talking to the Volar team to streamline the IntelliSense experience for MDX, Vue, and other similar languages that embed JavaScript.

[HomyeeKing]

@remcohaszing thanks for your response. it does have IntelliSense while inputting props, but no type check

also, I would like it works in code block too

// foo.mdx

```tsx
 // some tsx code here also have intellisense and  type check
```

[remcohaszing]

I am not able to reproduce this issue. Is the MDX file be excluded by your include / exclude configuration? Could you create a minimal reproduction?

[remcohaszing]

And ESLint is unrelated to this. I know it’s mentioned in the readme, so I understand the confusion.

[HomyeeKing]

https://github.com/HomyeeKing/reproduce-mdx-type-check

here is the repo

[remcohaszing]

It’s actually working for me.

Are you using an old version of the MDX extension?

[HomyeeKing]

emmm... it suddenly works now and I have no idea why 🤷‍♂️
anyway thanks for your time!