❗ Import This is still in development. While the language server is being used by VS Code, it has not yet been tested with other clients.
The Markdown language server powers VS Code's built-in markdown support, providing tools for writing and browsing Markdown files. It runs as a separate executable and implements the language server protocol.
This server uses the Markdown Language Service to implement almost all of the language features. You can use that library if you need a library for working with Markdown instead of a full language server.
-
Completions for Markdown links.
-
Folding of Markdown regions, block elements, and header sections.
-
Smart selection for inline elements, block elements, and header sections.
-
Document Symbols for quick navigation to headers in a document.
-
Workspace Symbols for quick navigation to headers in the workspace
-
Document links for making Markdown links in a document clickable.
-
Find all references to headers and links across all Markdown files in the workspace.
-
Go to definition from links to headers or link definitions.
-
Rename of headers and links across all Markdown files in the workspace.
-
Find all references to a file. Uses a custom
markdown/getReferencesToFileInWorkspace
message. -
- Organize link definitions source action.
- Extract link to definition refactoring.
-
Updating links when a file is moved / renamed. Uses a custom
markdown/getEditForFileRenames
message. -
Pull diagnostics (validation) for links.
The client can send the following initialization options to the server:
markdownFileExtensions
Array file extensions that should be considered as Markdown. These should not include the leading.
. For example:['md', 'mdown', 'markdown']
.
Clients may send a workspace/didChangeConfiguration
notification to notify the server of settings changes.
The server supports the following settings:
markdown
-
suggest
paths
enabled
— Enable/disable path suggestions.
-
occurrencesHighlight
enabled
— Enable/disable highlighting of link occurrences.
-
validate
enabled
— Enable/disable all validation.referenceLinks
enabled
— Enable/disable validation of reference links:[text][ref]
fragmentLinks
enabled
— Enable/disable validation of links to fragments in the current files:[text](#head)
fileLinks
enabled
— Enable/disable validation of links to file in the workspace.markdownFragmentLinks
— Enable/disable validation of links to headers in other Markdown files. Useinherit
to inherit thefragmentLinks
setting.
ignoredLinks
— Array of glob patterns for files that should not be validated.unusedLinkDefinitions
enabled
— Enable/disable validation of unused link definitions.
duplicateLinkDefinitions
enabled
— Enable/disable validation of duplicated link definitions.
-
To support all of the features of the language server, the client needs to implement a few custom request types. The definitions of these request types can be found in protocol.ts
Get the tokens for a Markdown file. Clients are expected to use Markdown-it for this.
We require that clients bring their own version of Markdown-it so that they can customize/extend Markdown-it.
Read the contents of a file in the workspace.
Read the contents of a directory in the workspace.
Check if a given file/directory exists in the workspace.
Create a file watcher. This is needed for diagnostics support.
Delete a previously created file watcher.
Get a list of all markdown files in the workspace.
The source code of the Markdown language server can be found in the VSCode repository at extensions/markdown-language-features/server.
File issues and pull requests in the VSCode GitHub Issues. See the document How to Contribute on how to build and run from source.
Most of the functionality of the server is located in libraries:
- vscode-markdown-languageservice contains the implementation of all features as a reusable library.
- vscode-languageserver-node contains the implementation of language server for NodeJS.
Help on any of these projects is very welcome.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
Copyright (c) Microsoft Corporation. All rights reserved.
Licensed under the MIT License.