Package Exports
- markdownlint-cli2
This package does not declare an exports field, so the exports above have been automatically detected and optimized by JSPM instead. If any package subpath is missing, it is recommended to post an issue to the original package (markdownlint-cli2) to support the "exports" field. If that is not possible, create a JSPM override to customize the exports field for this package.
Readme
markdownlint-cli2
A fast, flexible, configuration-based command-line interface for linting Markdown/CommonMark files with the
markdownlintlibrary
Install
As a global CLI:
npm install markdownlint-cli2 --globalAs a development dependency of the current package:
npm install markdownlint-cli2 --save-devOverview
markdownlintis a library for linting Markdown/ CommonMark files on Node.js using the markdown-it parser.markdownlint-cliis a traditional command-line interface formarkdownlint.markdownlint-cli2is a slightly unconventional command-line interface formarkdownlint.markdownlint-cli2is configuration-based and prioritizes speed and simplicity.markdownlint-cli2supports all the features ofmarkdownlint-cli(sometimes a little differently).vscode-markdownlintis amarkdownlintextension for the Visual Studio Code editor.markdownlint-cli2is designed to work well in conjunction withvscode-markdownlint.
Use
markdownlint-cli2 version X.Y.Z by David Anson (https://dlaa.me/)
https://github.com/DavidAnson/markdownlint-cli2
Syntax: markdownlint-cli2 glob0 [glob1] [...] [globN]
Glob expressions (from the globby library):
- * matches any number of characters, but not /
- ? matches a single character, but not /
- ** matches any number of characters, including / (when it's the only thing in a path part)
- {} allows for a comma-separated list of "or" expressions
- ! or # at the beginning of a pattern negate the match
Dot-only glob:
- The command "markdownlint-cli2 ." would lint every file in the current directory tree which is probably not intended
- Instead, it is mapped to "markdownlint-cli2 *.{md,markdown}" which lints all Markdown files in the current directory
- To lint every file in the current directory tree, the command "markdownlint-cli2 **" can be used instead
Configuration via:
- .markdownlint-cli2.jsonc
- .markdownlint-cli2.js
- .markdownlint.jsonc or .markdownlint.json
- .markdownlint.yaml or .markdownlint.yml
- .markdownlint.js
Cross-platform compatibility:
- UNIX and Windows shells expand globs according to different rules, so quoting glob arguments is recommended
- Shells that expand globs do not support negated patterns (!node_modules), so quoting negated globs is required
- Some Windows shells do not handle single-quoted (') arguments correctly, so double-quotes (") are recommended
- Some UNIX shells handle exclamation (!) in double-quotes specially, so hashtag (#) is recommended for negated globs
- Some shells use backslash (\) to escape special characters, so forward slash (/) is the recommended path separator
Therefore, the most compatible glob syntax for cross-platform support:
$ markdownlint-cli2 "**/*.md" "#node_modules"Exit Codes
0: Linting was successful and there were no errors1: Linting was successful and there were errors2: Linting was not completed due to a runtime issue
Rule List
- See the Rules / Aliases and
Tags sections of the
markdownlintdocumentation.
Glob expressions
- Globbing is performed by the globby library; refer to that documentation for more information and examples.
Configuration
- See the Configuration section of the
markdownlintdocumentation for information about the inline comment syntax for enabling and disabling rules with HTML comments.
.markdownlint-cli2.jsonc
- The format of this file is a JSONC object similar to the
markdownlintoptionsobject. - Valid properties are:
config:markdownlintconfigobject to configure rules for this part of the directory tree- If a
.markdownlint.{jsonc,json,yaml,yml,js}file (see below) is present in the same directory, it overrides the value of this property
- If a
customRules:ArrayofStringsof module names/paths of custom rules to load and use when linting- Each
Stringis passed as theidparameter to Node's require function - Relative paths are resolved based on the location of the
JSONCfile
- Each
fix:Booleanvalue to enable fixing of linting errors reported by rules that emit fix information- Fixes are made directly to the relevant file(s); no backup is created
frontMatter:Stringdefining theRegExpused to match and ignore any front matter at the beginning of a document- The
Stringis passed as thepatternparameter to theRegExpconstructor - For example:
(^---\s*$[^]*?^---\s*$)(\r\n|\r|\n|$)
- The
ignores:ArrayofStringsdefining glob expressions to ignore when linting- This setting has the best performance when applied to the directory from
which
markdownlint-cli2is run- In this case, glob expressions are negated (by adding a leading
!) and appended to the command-line arguments before file enumeration - The setting is not inherited by nested configuration files in this case
- In this case, glob expressions are negated (by adding a leading
- When this setting is applied in subdirectories, ignoring of files is done
after file enumeration, so large directories can negatively impact
performance
- Nested configuration files inherit and reapply the setting to the contents of nested directories in this case
- This setting has the best performance when applied to the directory from
which
markdownItPlugins:ArrayofArrays, each of which has aStringnaming a markdown-it plugin followed by parameters- Plugins can be used to add support for additional Markdown syntax
- Relative paths are resolved based on the location of the
JSONCfile - For example:
[ [ "plugin-name", param_0, param_1, ... ], ... ]
noInlineConfig:Booleanvalue to disable the support of HTML comments within Markdown content- For example:
<!-- markdownlint-disable some-rule -->
- For example:
outputFormatters:ArrayofArrays, each of which has aStringnaming a markdownlint-cli2-formatter followed by parameters- Formatters can be used to customize the tool's output for different scenarios
- Relative paths are resolved based on the location of the
JSONCfile - For example:
[ [ "formatter-name", param_0, param_1, ... ], ... ] - This setting affects output for the entire pass, so is valid only in
the directory from which
markdownlint-cli2is run
- Settings in this file apply to the directory it is in and all subdirectories.
- Settings merge with those applied by any versions of this file in a parent directory.
- For example:
.markdownlint-cli2.jsoncwith all properties set
.markdownlint-cli2.js
- The format of this file is a CommonJS module that exports
the
.markdownlint-cli2.jsoncobject described above. - Other details are the same as for
.markdownlint-cli2.jsoncdescribed above. - If a
.markdownlint-cli2.jsoncfile is present in the same directory, it takes precedence. - For example:
.markdownlint-cli2.js
.markdownlint.jsonc or .markdownlint.json
- The format of this file is a JSONC or JSON object matching
the
markdownlintconfigobject. - Settings in this file apply to the directory it is in and all subdirectories
- Settings override those applied by any versions of this file in a parent directory.
- If
jsoncandjsonfiles are present in the same directory, thejsoncversion takes precedence. - To merge the settings of these files or share configuration, use the
extendsproperty (documented in the link above). - Both file types support comments in JSON.
- For example:
.markdownlint.jsonc
.markdownlint.yaml or .markdownlint.yml
- The format of this file is a YAML object representing the
markdownlintconfigobject. - Other details are the same as for
jsonc/jsonfiles described above. - If
yamlandymlfiles are present in the same directory, theyamlversion takes precedence. - If a
jsoncorjsonfile is present in the same directory, it takes precedence. - For example:
.markdownlint.yaml
.markdownlint.js
- The format of this file is a CommonJS module that exports
the
markdownlintconfigobject. - Other details are the same as for
jsonc/jsonfiles described above. - If a
jsonc,json,yaml, orymlfile is present in the same directory, it takes precedence. - For example:
.markdownlint.js
Compatibility
markdownlint-cli
- The glob implementation and handling of pattern matching is slightly different.
- Configuration files are supported in every directory (vs. only one at the root).
- The
INIconfig format,.markdownlintrc, and.markdownlintignoreare not supported.
vscode-markdownlint
.markdownlintrcand.markdownlintignoreare not supported.
History
- 0.0.2 - Initial release
- 0.0.3 - Feature parity with
markdownlint-cli - 0.0.4 - Support output formatters and
markdown-itplugins - 0.0.5 - Improve support for ignoring files
- 0.0.6 - Improve handling of very large directory trees
- 0.0.7 - Support
.markdownlint-cli2.jsand.markdownlint.js