remark-lint
rule to warn when fenced code markers are
inconsistent.
- What is this?
- When should I use this?
- Presets
- Install
- Use
- API
- Recommendation
- Fix
- Examples
- Compatibility
- Contribute
- License
This package checks fenced code block markers.
You can use this package to check that fenced code block markers are consistent.
This plugin is included in the following presets:
Preset | Options |
---|---|
remark-preset-lint-consistent |
'consistent' |
remark-preset-lint-markdown-style-guide |
'`' |
This package is ESM only. In Node.js (version 16+), install with npm:
npm install remark-lint-fenced-code-marker
In Deno with esm.sh
:
import remarkLintFencedCodeMarker from 'https://esm.sh/remark-lint-fenced-code-marker@4'
In browsers with esm.sh
:
<script type="module">
import remarkLintFencedCodeMarker from 'https://esm.sh/remark-lint-fenced-code-marker@4?bundle'
</script>
On the API:
import remarkLint from 'remark-lint'
import remarkLintFencedCodeMarker from 'remark-lint-fenced-code-marker'
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(remarkLintFencedCodeMarker)
.use(remarkStringify)
.process(file)
console.error(reporter(file))
On the CLI:
remark --frail --use remark-lint --use remark-lint-fenced-code-marker .
On the CLI in a config file (here a package.json
):
…
"remarkConfig": {
"plugins": [
…
"remark-lint",
+ "remark-lint-fenced-code-marker",
…
]
}
…
This package exports no identifiers.
It exports the TypeScript types
Marker
and
Options
.
The default export is
remarkLintFencedCodeMarker
.
Warn when fenced code markers are inconsistent.
options
(Options
, default:'consistent'
) — preferred style or whether to detect the first style and warn for further differences
Transform (Transformer
from unified
).
Marker (TypeScript type).
type Marker = '`' | '~'
Configuration (TypeScript type).
type Options = Marker | 'consistent'
Tildes are uncommon.
So it’s recommended to configure this rule with '`'
.
remark-stringify
formats fenced code with grave
accents by default.
Pass fence: '~'
to always use tildes.
Indented code blocks are not affected by this rule:
mercury()
No messages.
When configured with '`'
.
```javascript
mercury()
```
```
venus()
```
No messages.
When configured with '~'
.
~~~javascript
mercury()
~~~
~~~
venus()
~~~
No messages.
```javascript
mercury()
```
~~~
venus()
~~~
5:1-7:4: Unexpected fenced code marker `~`, expected `` ` ``
~~~javascript
mercury()
~~~
```
venus()
```
5:1-7:4: Unexpected fenced code marker `` ` ``, expected `~`
When configured with '🌍'
.
1:1: Unexpected value `🌍` for `options`, expected ``'`'``, `'~'`, or `'consistent'`
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-fenced-code-marker@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.