remark-lint rule to warn when the whitespace after list item markers violate
a given style.
- What is this?
- When should I use this?
- Presets
- Install
- Use
- API
- Recommendation
- Fix
- Examples
- Compatibility
- Contribute
- License
This package checks the style of whitespace after list item markers.
You can use this package to check that the style of whitespace after list item markers and before content is consistent.
This plugin is included in the following presets:
| Preset | Options |
|---|---|
remark-preset-lint-markdown-style-guide |
'mixed' |
remark-preset-lint-recommended |
'one' |
This package is ESM only. In Node.js (version 16+), install with npm:
npm install remark-lint-list-item-indentIn Deno with esm.sh:
import remarkLintListItemIndent from 'https://esm.sh/remark-lint-list-item-indent@4'In browsers with esm.sh:
<script type="module">
import remarkLintListItemIndent from 'https://esm.sh/remark-lint-list-item-indent@4?bundle'
</script>On the API:
import remarkLint from 'remark-lint'
import remarkLintListItemIndent from 'remark-lint-list-item-indent'
import remarkParse from 'remark-parse'
import remarkStringify from 'remark-stringify'
import {read} from 'to-vfile'
import {unified} from 'unified'
import {reporter} from 'vfile-reporter'
const file = await read('example.md')
await unified()
.use(remarkParse)
.use(remarkLint)
.use(remarkLintListItemIndent)
.use(remarkStringify)
.process(file)
console.error(reporter(file))On the CLI:
remark --frail --use remark-lint --use remark-lint-list-item-indent .On the CLI in a config file (here a package.json):
…
"remarkConfig": {
"plugins": [
…
"remark-lint",
+ "remark-lint-list-item-indent",
…
]
}
…This package exports no identifiers.
It exports the TypeScript type
Options.
The default export is
remarkLintListItemIndent.
Warn when the whitespace after list item markers violate a given style.
options(Options, default:'one') — preferred style
Transform (Transformer from unified).
Configuration (TypeScript type).
'mixed'— prefer'one'for tight lists and'tab'for loose lists'one'— prefer the size of the bullet and a single space'tab'— prefer the size of the bullet and a single space to the next tab stop
type Options = 'mixed' | 'one' | 'tab'First some background.
The number of spaces that occur after list markers (*, -, and + for
unordered lists and . and ) for unordered lists) and before the content
on the first line,
defines how much indentation can be used for further lines.
At least one space is required and up to 4 spaces are allowed.
If there is no further content after the marker then it’s a blank line which
is handled as if there was one space.
If there are 5 or more spaces and then content then it’s also seen as one
space and the rest is seen as indented code.
Regardless of ordered and unordered,
there are two kinds of lists in markdown,
tight and loose.
Lists are tight by default but if there is a blank line between two list
items or between two blocks inside an item,
that turns the whole list into a loose list.
When turning markdown into HTML,
paragraphs in tight lists are not wrapped in <p> tags.
How indentation of lists works in markdown has historically been a mess,
especially with how they interact with indented code.
CommonMark made that a lot better,
but there remain (documented but complex) edge cases and some behavior
intuitive.
Due to this, 'tab' works the best in most markdown parsers and in
CommonMark.
Currently the situation between markdown parsers is better,
so the default 'one',
which seems to be the most common style used by authors,
is okay.
remark-stringify uses listItemIndent: 'one'
by default.
listItemIndent: 'mixed' or listItemIndent: 'tab' is also supported.
*␠Mercury.
*␠Venus.
111.␠Earth
␠␠␠␠␠and Mars.
*␠**Jupiter**.
␠␠Jupiter is the fifth planet from the Sun and the largest in the Solar
␠␠System.
*␠Saturn.
␠␠Saturn is the sixth planet from the Sun and the second-largest in the Solar System, after Jupiter.No messages.
When configured with 'mixed'.
*␠Mercury.
*␠Venus.
111.␠Earth
␠␠␠␠␠and Mars.
*␠␠␠**Jupiter**.
␠␠␠␠Jupiter is the fifth planet from the Sun and the largest in the Solar
␠␠␠␠System.
*␠␠␠Saturn.
␠␠␠␠Saturn is the sixth planet from the Sun and the second-largest in the Solar System, after Jupiter.No messages.
When configured with 'mixed'.
*␠␠␠Mercury.
*␠␠␠Venus.
111.␠␠␠␠Earth
␠␠␠␠␠␠␠␠and Mars.
*␠**Jupiter**.
␠␠Jupiter is the fifth planet from the Sun and the largest in the Solar
␠␠System.
*␠Saturn.
␠␠Saturn is the sixth planet from the Sun and the second-largest in the Solar System, after Jupiter.1:5: Unexpected `3` spaces between list item marker and content in tight list, expected `1` space, remove `2` spaces
2:5: Unexpected `3` spaces between list item marker and content in tight list, expected `1` space, remove `2` spaces
4:9: Unexpected `4` spaces between list item marker and content in tight list, expected `1` space, remove `3` spaces
7:3: Unexpected `1` space between list item marker and content in loose list, expected `3` spaces, add `2` spaces
12:3: Unexpected `1` space between list item marker and content in loose list, expected `3` spaces, add `2` spaces
When configured with 'one'.
*␠Mercury.
*␠Venus.
111.␠Earth
␠␠␠␠␠and Mars.
*␠**Jupiter**.
␠␠Jupiter is the fifth planet from the Sun and the largest in the Solar
␠␠System.
*␠Saturn.
␠␠Saturn is the sixth planet from the Sun and the second-largest in the Solar System, after Jupiter.No messages.
When configured with 'one'.
*␠␠␠Mercury.
*␠␠␠Venus.
111.␠␠␠␠Earth
␠␠␠␠␠␠␠␠and Mars.
*␠␠␠**Jupiter**.
␠␠␠␠Jupiter is the fifth planet from the Sun and the largest in the Solar
␠␠␠␠System.
*␠␠␠Saturn.
␠␠␠␠Saturn is the sixth planet from the Sun and the second-largest in the Solar System, after Jupiter.1:5: Unexpected `3` spaces between list item marker and content, expected `1` space, remove `2` spaces
2:5: Unexpected `3` spaces between list item marker and content, expected `1` space, remove `2` spaces
4:9: Unexpected `4` spaces between list item marker and content, expected `1` space, remove `3` spaces
7:5: Unexpected `3` spaces between list item marker and content, expected `1` space, remove `2` spaces
12:5: Unexpected `3` spaces between list item marker and content, expected `1` space, remove `2` spaces
When configured with 'tab'.
*␠␠␠Mercury.
*␠␠␠Venus.
111.␠␠␠␠Earth
␠␠␠␠␠␠␠␠and Mars.
*␠␠␠**Jupiter**.
␠␠␠␠Jupiter is the fifth planet from the Sun and the largest in the Solar
␠␠␠␠System.
*␠␠␠Saturn.
␠␠␠␠Saturn is the sixth planet from the Sun and the second-largest in the Solar System, after Jupiter.No messages.
When configured with 'tab'.
*␠Mercury.
*␠Venus.
111.␠Earth
␠␠␠␠␠and Mars.
*␠**Jupiter**.
␠␠Jupiter is the fifth planet from the Sun and the largest in the Solar
␠␠System.
*␠Saturn.
␠␠Saturn is the sixth planet from the Sun and the second-largest in the Solar System, after Jupiter.1:3: Unexpected `1` space between list item marker and content, expected `3` spaces, add `2` spaces
2:3: Unexpected `1` space between list item marker and content, expected `3` spaces, add `2` spaces
4:6: Unexpected `1` space between list item marker and content, expected `4` spaces, add `3` spaces
7:3: Unexpected `1` space between list item marker and content, expected `3` spaces, add `2` spaces
12:3: Unexpected `1` space between list item marker and content, expected `3` spaces, add `2` spaces
When configured with '🌍'.
1:1: Unexpected value `🌍` for `options`, expected `'mixed'`, `'one'`, or `'tab'`
When configured with 'mixed'.
👉 Note: this example uses GFM (
remark-gfm).
*␠[x] Mercury.
1.␠␠[ ] Venus.
2.␠␠[ ] Earth.No messages.
When configured with 'one'.
👉 Note: this example uses GFM (
remark-gfm).
*␠[x] Mercury.
1.␠[ ] Venus.
2.␠[ ] Earth.No messages.
When configured with 'tab'.
👉 Note: this example uses GFM (
remark-gfm).
*␠␠␠[x] Mercury.
1.␠␠[ ] Venus.
2.␠␠[ ] Earth.No messages.
When configured with 'mixed'.
Loose lists have blank lines between items:
*␠␠␠Mercury.
*␠␠␠Venus.
…or between children of items:
1.␠␠Earth.
␠␠␠␠Earth is the third planet from the Sun and the only astronomical
␠␠␠␠object known to harbor life.No messages.
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-list-item-indent@4,
compatible with Node.js 16.
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.