remark plugins to check (lint) markdown code style.

Contents

• What is this?
• When should I use this?
• Presets
• Rules
• Configure
• Ignore warnings
• Examples
  • Example: check markdown on the API
  • Example: check and format markdown on the API
  • Example: check markdown on the CLI
  • Example: check and format markdown on the CLI
• Integrations
• Syntax
• Compatibility
• Security
• Contribute
• License

What is this?

You can use this to check markdown. Say we have a markdown file doc/example.md that contains:

11) Hello, _Jupiter_ and *Neptune*!

Then assuming we installed dependencies and run:

1npx remark doc/ --use remark-preset-lint-consistent --use remark-preset-lint-recommended

We would get a report like this:

1doc/example.md
21:2           warning Unexpected ordered list marker `)`, expected `.`                  ordered-list-marker-style remark-lint
31:25-1:34     warning Unexpected emphasis marker `*`, expected `_`                      emphasis-marker           remark-lint
4  [cause]:
5    1:11-1:20 info    Emphasis marker style `'_'` first defined for `'consistent'` here emphasis-marker           remark-lint
6
7⚠ 2 warnings

This GitHub repository is a monorepo that contains ±70 plugins (each a rule that checks one specific thing) and 3 presets (combinations of rules configured to check for certain styles).

These packages are build on unified (remark). unified is a project that inspects and transforms content with abstract syntax trees (ASTs). remark adds support for markdown to unified. mdast is the markdown AST that remark uses. These lint rules inspect mdast.

When should I use this?

This project is useful when developers or technical writers are authoring documentation in markdown and you want to ensure that the markdown is consistent, free of bugs, and works well across different markdown parsers.

These packages are quite good at checking markdown. They especially shine when combined with other remark plugins and at letting you make your own rules.

Presets

Presets are combinations of rules configured to check for certain styles. The following presets only contain lint rules but you can make your own that include any remark plugins or other presets. The presets that are maintained here:

• remark-preset-lint-consistent — rules that enforce consistency
• remark-preset-lint-markdown-style-guide — rules that enforce the markdown style guide
• remark-preset-lint-recommended — rules that prevent mistakes or stuff that fails across vendors.

Rules

The rules that are maintained here:

• remark-lint-blockquote-indentation — warn when block quotes are either indented too much or too little
• remark-lint-checkbox-character-style — warn when list item checkboxes violate a given style
• remark-lint-checkbox-content-indent — warn when list item checkboxes are followed by too much whitespace
• remark-lint-code-block-style — warn when code blocks do not adhere to a given style
• remark-lint-definition-case — warn when definition labels are not lowercase
• remark-lint-definition-spacing — warn when consecutive whitespace is used in a definition
• remark-lint-emphasis-marker — warn when emphasis markers violate the given style
• remark-lint-fenced-code-flag — warn when fenced code blocks occur without language flag
• remark-lint-fenced-code-marker — warn when fenced code markers violate the given style
• remark-lint-file-extension — warn when the file’s extension violates the given style
• remark-lint-final-definition — warn when definitions are not placed at the end of the file
• remark-lint-final-newline — warn when a newline at the end of a file is missing
• remark-lint-first-heading-level — warn when the first heading has a level other than a specified value
• remark-lint-hard-break-spaces — warn when too many spaces are used to create a hard break
• remark-lint-heading-increment — warn when headings increment with more than 1 level at a time
• remark-lint-heading-style — warn when heading style violates the given style
• remark-lint-linebreak-style — warn when linebreaks violate a given or detected style
• remark-lint-link-title-style — warn when link and definition titles occur with incorrect quotes
• remark-lint-list-item-bullet-indent — warn when list item bullets are indented
• remark-lint-list-item-content-indent — warn when the content of a list item has mixed indentation
• remark-lint-list-item-indent — warn when the spacing between a list item’s bullet and its content violates a given style
• remark-lint-list-item-spacing — warn when list looseness is incorrect
• remark-lint-maximum-heading-length — warn when headings are too long
• remark-lint-maximum-line-length — warn when lines are too long
• remark-lint-no-blockquote-without-marker — warn when blank lines without markers (`>`) are found in a block quote
• remark-lint-no-consecutive-blank-lines — warn for too many consecutive blank lines
• remark-lint-no-duplicate-defined-urls — warn on definitions that define the same urls
• remark-lint-no-duplicate-definitions — warn on duplicate definitions
• remark-lint-no-duplicate-headings — warn on duplicate headings
• remark-lint-no-duplicate-headings-in-section — warn on duplicate headings in a section
• remark-lint-no-emphasis-as-heading — warn when emphasis or importance is used instead of a heading
• remark-lint-no-empty-url — warn on empty URLs in links and images
• remark-lint-no-file-name-articles — warn when file name start with an article
• remark-lint-no-file-name-consecutive-dashes — warn when file names contain consecutive dashes
• remark-lint-no-file-name-irregular-characters — warn when file names contain irregular characters
• remark-lint-no-file-name-mixed-case — warn when file names use mixed case
• remark-lint-no-file-name-outer-dashes — warn when file names contain initial or final dashes
• remark-lint-no-heading-content-indent — warn when heading content is indented
• remark-lint-no-heading-indent — warn when headings are indented
• remark-lint-no-heading-like-paragraph — for too many hashes (h7+ “headings”)
• remark-lint-no-heading-punctuation — warn when headings end in illegal characters
• remark-lint-no-html — warn when HTML nodes are used
• remark-lint-no-literal-urls — warn when URLs without angle brackets are used
• remark-lint-no-missing-blank-lines — warn when missing blank lines
• remark-lint-no-multiple-toplevel-headings — warn when multiple top level headings are used
• remark-lint-no-paragraph-content-indent — warn when the content in paragraphs are indented
• remark-lint-no-reference-like-url — warn when URLs are also defined identifiers
• remark-lint-no-shell-dollars — warn when shell code is prefixed by dollars
• remark-lint-no-shortcut-reference-image — warn when shortcut reference images are used
• remark-lint-no-shortcut-reference-link — warn when shortcut reference links are used
• remark-lint-no-table-indentation — warn when tables are indented
• remark-lint-no-tabs — warn when hard tabs are used instead of spaces
• remark-lint-no-undefined-references — warn when references to undefined definitions are found
• remark-lint-no-unneeded-full-reference-image — warn when full reference images are used if they can be collapsed
• remark-lint-no-unneeded-full-reference-link — warn when full reference links are used if they can be collapsed
• remark-lint-no-unused-definitions — warn when unused definitions are found
• remark-lint-ordered-list-marker-style — warn when the markers of ordered lists violate a given style
• remark-lint-ordered-list-marker-value — warn when the marker value of ordered lists violates a given style
• remark-lint-rule-style — warn when horizontal rules violate a given style
• remark-lint-strikethrough-marker — warn when strikethrough markers violate the given style
• remark-lint-strong-marker — warn when importance (strong) markers violate the given style
• remark-lint-table-cell-padding — warn when table cells are incorrectly padded
• remark-lint-table-pipe-alignment — warn when table pipes are not aligned
• remark-lint-table-pipes — warn when table rows are not fenced with pipes
• remark-lint-unordered-list-marker-style — warn when markers of unordered lists violate a given style

You can make and share your own rules, which can be used just like the rules maintained here. The following rules are maintained by the community:

• remark-lint-alphabetize-lists — ensure list items are in alphabetical order
• remark-lint-appropriate-heading — check that the top level heading matches the directory name
• remark-lint-are-links-valid — check if your links are reachable and/or unique
• remark-lint-blank-lines-1-0-2 — ensure a specific number of lines between blocks
• remark-lint-books-links — ensure links in lists of books follow a standard format
• remark-lint-check-toc — ensure TOC is correct
• remark-lint-code — lint fenced code blocks by corresponding language tags, currently supporting ESLint
• remark-lint-code-block-split-list — ensure code block inside list doesn't split the list
• remark-lint-double-link — ensure the same URL is not linked multiple times.
• remark-lint-emoji-limit — enforce a limit of emoji per paragraph
• remark-lint-fenced-code-flag-case — warn when fenced code blocks have improperly cased language flags
• remark-lint-frontmatter-schema — validate YAML frontmatter against a JSON schema
• remark-lint-heading-capitalization — ensure headings capitalization is correct
• remark-lint-heading-length — ensure headings have the appropriate length
• remark-lint-heading-whitespace — ensure heading parsing is not broken by weird whitespace
• remark-lint-heading-word-length — warn when headings have too many or too few words with unicode support
• remark-lint-list-item-style — warn when list items violate a given capitalization or punctuation style
• remark-lint-match-punctuation — ensures punctuations are used in pairs if necessary.
• remark-lint-mdash-style — ensure em-dash (—) style follows a standard format
• remark-lint-no-chinese-punctuation-in-number — ensures that Chinese punctuation’s not used in numbers
• remark-lint-no-dead-urls — check that external links are alive
• remark-lint-no-empty-sections — ensure every heading is followed by content (forming a section)
• remark-lint-no-long-code — ensures that each line in code block won't be too long.
• remark-lint-no-repeat-punctuation — ensures punctuation is not repeated
• remark-lint-no-url-trailing-slash — ensure that the href of links has no trailing slash
• remark-lint-spaces-around-number — ensures there are spaces around number and Chinese.
• remark-lint-spaces-around-word — ensures there are spaces around English word and Chinese.
• remark-lint-write-good — wrapper for write-good

For help creating your own rule, it’s suggested to look at existing rules and to follow this tutorial.

Configure

All rules can be configured in one standard way:

1import {remark} from 'remark'
2import remarkLintFinalNewline from 'remark-lint-final-newline'
3import remarkLintMaximumLineLength from 'remark-lint-maximum-line-length'
4import remarkLintUnorderedListMarkerStyle from 'remark-lint-unordered-list-marker-style'
5
6remark()
7  // Pass `false` to turn a rule off — the code no longer runs:
8  .use(remarkLintFinalNewline, false)
9  // Pass `true` to turn a rule on again:
10  .use(remarkLintFinalNewline, true)
11  // You can also configure whether messages by the rule should be ignored,
12  // are seen as code style warnings (default), or are seen as exceptions.
13  // Ignore messages with `'off'` or `0` as the first value of an array:
14  .use(remarkLintFinalNewline, ['off'])
15  .use(remarkLintFinalNewline, [0])
16  // Use `'warn'`, `'on'`, or `1` to treat messages as code style warnings:
17  .use(remarkLintFinalNewline, ['warn'])
18  .use(remarkLintFinalNewline, ['on'])
19  .use(remarkLintFinalNewline, [1])
20  // Use `'error'` or `2` to treat messages as exceptions:
21  .use(remarkLintFinalNewline, ['error'])
22  .use(remarkLintFinalNewline, [2])
23  // Some rules accept options, and what they exactly accept is different for
24  // each rule (sometimes a string, a number, or an object).
25  // The following rule accepts a string:
26  .use(remarkLintUnorderedListMarkerStyle, '*')
27  .use(remarkLintUnorderedListMarkerStyle, ['on', '*'])
28  .use(remarkLintUnorderedListMarkerStyle, [1, '*'])
29  // The following rule accepts a number:
30  .use(remarkLintMaximumLineLength, 72)
31  .use(remarkLintMaximumLineLength, ['on', 72])
32  .use(remarkLintMaximumLineLength, [1, 72])

See use() in unifieds readme for more info on how to use plugins.

🧑‍🏫 Info: messages in remark-lint are warnings instead of errors. Other linters (such as ESLint) almost always use errors. Why? Those tools only check code style. They don’t generate, transform, and format code, which is what remark and unified focus on, too. Errors in unified mean the same as an exception in your JavaScript code: a crash. That’s why we use warnings instead, because we continue checking more markdown and continue running more plugins.

Ignore warnings

You can use HTML comments to hide or show warnings from within markdown. Turn off all remark lint messages with <!--lint disable--> and turn them on again with <!--lint enable-->:

1<!--lint disable-->
2
3[Naiad]: https://naiad.neptune
4
5[Thalassa]: https://thalassa.neptune
6
7<!--lint enable-->

You can toggle specific rules by using their names without remark-lint-:

1<!--lint disable no-unused-definitions definition-case-->
2
3[Naiad]: https://naiad.neptune
4
5[Thalassa]: https://thalassa.neptune
6
7<!--lint enable no-unused-definitions definition-case-->

You can ignore a message in the next block with <!--lint ignore-->:

1<!--lint ignore-->
2
3[Naiad]: https://naiad.neptune

ignore also accepts a list of rules:

1<!--lint ignore no-unused-definitions definition-case-->
2
3[Naiad]: https://naiad.neptune

👉 Note: you’ll typically need blank lines between HTML comments and other constructs. More info is available at the package that handles comments, remark-message-control.

💡 Tip: MDX comments are supported when remark-mdx is used:

1{/* lint ignore no-unused-definitions definition-case */}

Examples

Example: check markdown on the API

The following example checks that markdown code style is consistent and follows some best practices. It also reconfigures a rule. First install dependencies:

1npm install vfile-reporter remark remark-preset-lint-consistent remark-preset-lint-recommended remark-lint-list-item-indent --save-dev

Then create a module example.js that contains:

1import {remark} from 'remark'
2import remarkLintListItemIndent from 'remark-lint-list-item-indent'
3import remarkPresetLintConsistent from 'remark-preset-lint-consistent'
4import remarkPresetLintRecommended from 'remark-preset-lint-recommended'
5import {reporter} from 'vfile-reporter'
6
7const file = await remark()
8  // Check that markdown is consistent.
9  .use(remarkPresetLintConsistent)
10  // Few recommended rules.
11  .use(remarkPresetLintRecommended)
12  // `remark-lint-list-item-indent` is configured with `one` in the
13  // recommended preset, but if we’d prefer something else, it can be
14  // reconfigured:
15  .use(remarkLintListItemIndent, 'tab')
16  .process('1) Hello, _Jupiter_ and *Neptune*!')
17
18console.error(reporter(file))

Running that with node example.js yields:

11:2           warning Unexpected ordered list marker `)`, expected `.`                                              ordered-list-marker-style remark-lint
21:4           warning Unexpected `1` space between list item marker and content, expected `2` spaces, add `1` space list-item-indent          remark-lint
31:25-1:34     warning Unexpected emphasis marker `*`, expected `_`                                                  emphasis-marker           remark-lint
4  [cause]:
5    1:11-1:20 info    Emphasis marker style `'_'` first defined for `'consistent'` here                             emphasis-marker           remark-lint
61:35          warning Unexpected missing final newline character, expected line feed (`\n`) at end of file          final-newline             remark-lint
7
8⚠ 4 warnings

Example: check and format markdown on the API

remark lint rules check markdown. remark-stringify (used in remark) formats markdown. When you configure lint rules and use remark to format markdown, you must manually synchronize their configuration:

1import {remark} from 'remark'
2import remarkLintEmphasisMarker from 'remark-lint-emphasis-marker'
3import remarkLintStrongMarker from 'remark-lint-strong-marker'
4import {reporter} from 'vfile-reporter'
5
6const file = await remark()
7  .use(remarkLintEmphasisMarker, '*')
8  .use(remarkLintStrongMarker, '*')
9  .use({
10    settings: {emphasis: '*', strong: '*'} // `remark-stringify` settings.
11  })
12  .process('_Hello_, __world__!')
13
14console.error(reporter(file))
15console.log(String(file))

Yields:

1    1:1-1:8  warning  Emphasis should use `*` as a marker  emphasis-marker  remark-lint
2  1:10-1:19  warning  Strong should use `*` as a marker    strong-marker    remark-lint
3
4⚠ 2 warnings

1*Hello*, **world**!

Observe that the lint rules check the input and afterwards remark formats using asterisks. If that output was given the the processor, the lint rules would be satisfied.

Example: check markdown on the CLI

This example checks markdown with remark-cli. It assumes you’re in a Node.js package. First install dependencies:

1npm install remark-cli remark-preset-lint-consistent remark-preset-lint-recommended remark-lint-list-item-indent --save-dev

Then add an npm script to your package.json:

1  /* … */
2  "scripts": {
3    /* … */
4    "check": "remark . --quiet --frail",
5    /* … */
6  },
7  /* … */

💡 Tip: add ESLint and such in the check script too.

Observe that the above change adds a check script, which can be run with npm run check. It runs remark on all markdown files (.), shows only warnings and errors (--quiet), and exits as failed on warnings (--frail). Run ./node_modules/.bin/remark --help for more info on the CLI.

Now add a remarkConfig to your package.json to configure remark:

1  /* … */
2  "remarkConfig": {
3    "plugins": [
4      "remark-preset-lint-consistent", // Check that markdown is consistent.
5      "remark-preset-lint-recommended", // Few recommended rules.
6      // `remark-lint-list-item-indent` is configured with `one` in the
7      // recommended preset, but if we’d prefer something else, it can be
8      // reconfigured:
9      [
10        "remark-lint-list-item-indent",
11        "tab"
12      ]
13    ]
14  },
15  /* … */

👉 Note: you must remove the comments in the above examples when copy/pasting them, as comments are not supported in package.json files.

Finally run the npm script to check markdown files in your project:

1npm run check

Example: check and format markdown on the CLI

remark lint rules check markdown. The CLI can format markdown. You can combine these features but have to manually synchronize their configuration. Please first follow the previous example (checking markdown on the CLI) and then change the npm script:

1  /* … */
2  "scripts": {
3    /* … */
4    "format": "remark . --frail --output --quiet",
5    /* … */
6  },
7  /* … */

The script is now called format to reflect what it does. It now includes an --output flag, which means it will overwrite existing files with changes.

Update remarkConfig:

1  /* … */
2  "remarkConfig": {
3    "settings": {
4      "emphasis": "*",
5      "strong": "*"
6    },
7    "plugins": [
8      "remark-preset-lint-consistent",
9      "remark-preset-lint-recommended",
10      ["remark-lint-list-item-indent", "tab"]
11      ["remark-lint-emphasis-marker", "*"],
12      ["remark-lint-strong-marker", "*"]
13    ]
14  },
15  /* … */

This now includes settings, which configures remark-stringify, and explicitly prefers asterisks for emphasis and strong. Install the new dependencies:

1npm install remark-lint-emphasis-marker remark-lint-strong-marker --save-dev

Finally run the npm script to format markdown files in your project:

1npm run format

👉 Note: running npm run format now checks and formats your files. The first time you run it, assuming you have underscores for emphasis and strong, it would first warn and then format. The second time you run it, no warnings should appear.

Integrations

• vscode-remark-lint (VS Code) — use remark-lint from Visual Studio Code
• SublimeLinter-contrib-remark-lint (Sublime) — use remark-lint from Sublime Text
• ale (Vim) — use remark-lint from Vim
• jest-runner-remark (Jest) — use remark with Jest

Syntax

Markdown is parsed by remark-parse (included in remark) according to CommonMark. You can combine it with other plugins to add syntax extensions. Notable examples that deeply integrate with it are remark-gfm, remark-mdx, remark-frontmatter, remark-math, and remark-directive.

Compatibility

Projects maintained by the unified collective are compatible with maintained versions of Node.js.

When we cut a new major release, we drop support for unmaintained versions of Node. This means we try to keep the current release line, remark-lint@9, compatible with Node.js 16.

Security

Use of remark-lint does not change the tree so there are no openings for cross-site scripting (XSS) attacks. Messages from linting rules may be hidden from user content though, causing builds to fail or pass.

Contribute

See contributing.md in remarkjs/.github for ways to get started. See support.md for ways to get help.

This project has a code of conduct. By interacting with this repository, organization, or community you agree to abide by its terms.

License

MIT © Titus Wormer