Project: remarkjs/remark-message-control

Package: remark-message-control@6.0.0

  1. Dependencies: 2·Dependents: 13
  2. remark plugin to enable, disable, and ignore messages with remark
  1. remark 186
  2. unified 154
  3. plugin 131
  4. markdown 115
  5. mdast 81
  6. remark-plugin 71
  7. marker 12
  8. message 8
  9. comment 7
  10. control 3


Build Coverage Downloads Size Sponsors Backers Chat

remark plugin to enable, disable, and ignore messages.



npm install remark-message-control


Say we have the following file, example.md:

<!--foo ignore-->

## Heading

And our script, example.js, looks as follows:

var vfile = require('to-vfile')
var report = require('vfile-reporter')
var remark = require('remark')
var control = require('remark-message-control')

  .use(control, {name: 'foo'})
  .process(vfile.readSync('example.md'), function(err, file) {
    console.error(report(err || file))

function warn() {
  return function(tree, file) {
    file.message('Whoops!', tree.children[1], 'foo:thing')

Now, running node example yields:

example.md: no issues found


remark().use(control, options)

Let comment markers control messages from a certain sources.


Name of markers that can control the message sources (string).

For example, {name: 'alpha'} controls alpha markers:

<!--alpha ignore-->

List of allowed ruleIds (Array.<string>, optional). When given, a warning is shown when someone tries to control an unknown rule.

For example, {name: 'alpha', known: ['bravo']} results in a warning if charlie is configured:

<!--alpha ignore charlie-->

Whether to treat all messages as turned off initially (boolean, default: false).


List of ruleIds to initially turn on if reset: true (Array.<string>, optional). By default (reset: false), all rules are turned on.


List of ruleIds to turn on if reset: false (Array.<string>, optional).


Sources that can be controlled with name markers (string or Array.<string>, default: options.name).



The disable keyword turns off all messages of the given rule identifiers. When without identifiers, all messages are turned off.

For example, to turn off certain messages:

<!--lint disable list-item-bullet-indent strong-marker-->

*   **foo**

A paragraph, and now another list.

  * __bar__

The enable keyword turns on all messages of the given rule identifiers. When without identifiers, all messages are turned on.

For example, to enable certain messages:

<!--lint enable strong-marker-->

**foo** and __bar__.

The ignore keyword turns off all messages of the given ruleIds occurring in the following node. When without ruleIds, all messages are ignored.

After the end of the following node, messages are turned on again.

For example, to turn off certain messages for the next node:

<!--lint ignore list-item-bullet-indent strong-marker-->

*   **foo**
  * __bar__


Use of remark-message-control does not involve rehype (hast) or user content so there are no openings for cross-site scripting (XSS) attacks. Messages may be hidden from user content though, causing builds to fail or pass, or changing a report.


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.


MIT © Titus Wormer