Enhancing the remark / VS Code experience

[remcohaszing]

Upcoming month I have some spare time I would like to spend on enhancing the experience of using remark with VS Code.

I still need to look into the exact issues I’ll run into, but roughly this is my idea:

• vscode-remark should use unified-language-server.
  • This will provide consistent behavior between language server based editor integrations.
  • This way plugins aren’t limited by any VS Code plugin runtime quirks.
• unified-language-server should use unified-engine.
  This ensures consistent behavior between the language server and CLI such as:
  • Loading of configuration files
  • Ignoring files
  • Processing files
• unified-language-server should be updated to adhere to the same code quality standards as the rest of the unified ecosystem.
  • Up-to-date dependencies
  • Types based on JSDoc
  • ESM
• vscode-remark should be able to lint files.
• vscode-remark should be able to autofix / format files.

Any feedback is welcome

[wooorm]

Awesome! :) Might be something to do/communicate with silvenon/vscode-mdx / mdx-js/vscode-mdx as well.

Related to linting (and remarkjs/remark-lint#276), I also have some thoughts on improving the existing rules, and perhaps adding more lint rules for directives/math/mdx/etc? It’s a different discussion but perhaps adjacent.

[remcohaszing]

Here’s a sneak preview of what this looks like in VSCode. 😄

It lints and formats the readme based on the latest version of remark-preset-wooorm. I don’t think VSCode extensions support ESM, but it doesn’t matter, as the language server works language agnostic. Also the entire VSCode extension is ~40 lines of code.

Screencast_2021-12-10_14.29.03.mp4