Remove TypeScript moving parts

[johnsoncodehk]

Initial checklist

• I read the support docs
• I read the contributing guide
• I agree to follow the code of conduct
• I searched issues and discussions and couldn’t find anything or linked relevant results below
• I made sure the docs are up to date
• I included tests (or that’s not needed)

Description of changes

When MDX TypeScript support is already provided through the TS plugin, the language server's TypeScript moving parts seem unnecessary, and I think it can be removed along with the tsdk option to simplify IDE integration.

• The tsdk option no longer needs to be passed by the language client, but is more simply added to the peerDependencies
• The language server TS tests need to be re-implemented based on @typescript/server-harness, which can be found at https://github.com/vuejs/language-tools/blob/master/packages/language-server/tests
• When language server doesn't need TS support, the file watcher doesn't seem to be needed anymore.
• I'm not sure if markPlugins, virtualCodePlugins are useful when language server doesn't need TS support. If it is, we need to refer to https://github.com/vuejs/language-tools/blob/073a7cb3bb823479ae5e9bff52850f529714571d/packages/language-server/index.ts#L62 to find tsconfig for each MDX file.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d8a93ce

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[remcohaszing]

Description of changes

When MDX TypeScript support is already provided through the TS plugin, the language server's TypeScript moving parts seem unnecessary, and I think it can be removed along with the tsdk option to simplify IDE integration.

I agree it’s better to configure TypeScript support with the TypeScript plugin, not the language server. It’s still supported by the language server, because this may be needed for some editors. I don’t know if this is the case.

• The language server TS tests need to be re-implemented based on @typescript/server-harness, which can be found at https://github.com/vuejs/language-tools/blob/master/packages/language-server/tests

It’s nice that we have this. :)

• When language server doesn't need TS support, the file watcher doesn't seem to be needed anymore.

Isn’t this needed for the markdown language service?

• I'm not sure if markPlugins, virtualCodePlugins are useful when language server doesn't need TS support. If it is, we need to refer to https://github.com/vuejs/language-tools/blob/073a7cb3bb823479ae5e9bff52850f529714571d/packages/language-server/index.ts#L62 to find tsconfig for each MDX file.

remark plugins register syntax extensions. For example, markdown directives may yield syntax errors unless the remark-directive plugin is added. virtualCodePlugins is needed for TypeScript indeed. But it’s also very useful to be able to inspect the generated virtual code. I think this can only be inspected via the language server, not via the TypeScript plugin.