$ npm install remark-lint-strong-marker
remark-lint
rule to warn when strong markers are inconsistent.
This package checks the style of strong markers.
You can use this package to check that strong is 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-strong-marker
In Deno with esm.sh
:
import remarkLintStrongMarker from 'https://esm.sh/remark-lint-strong-marker@4'
In browsers with esm.sh
:
<script type="module">
import remarkLintStrongMarker from 'https://esm.sh/remark-lint-strong-marker@4?bundle'
</script>
On the API:
import remarkLint from 'remark-lint'
import remarkLintStrongMarker from 'remark-lint-strong-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(remarkLintStrongMarker)
.use(remarkStringify)
.process(file)
console.error(reporter(file))
On the CLI:
remark --frail --use remark-lint --use remark-lint-strong-marker .
On the CLI in a config file (here a package.json
):
…
"remarkConfig": {
"plugins": [
…
"remark-lint",
+ "remark-lint-strong-marker",
…
]
}
…
This package exports no identifiers.
It exports the TypeScript types
Marker
and
Options
.
The default export is
remarkLintStrongMarker
.
unified().use(remarkLintStrongMarker[, options])
Warn when strong markers are inconsistent.
options
(Options
, default: 'consistent'
)
— preferred style or whether to detect the first style and warn for
further differencesTransform (Transformer
from unified
).
Marker
Marker (TypeScript type).
type Marker = '*' | '_'
Options
Configuration (TypeScript type).
type Options = Marker | 'consistent'
Whether asterisks or underscores are used affects how and whether strong works. Underscores are sometimes used to represent normal underscores inside words, so there are extra rules in markdown to support that. Asterisks are not used in natural language, so they don’t need these rules, and thus can form strong in more cases. Asterisks can also be used as the marker of more constructs than underscores: lists. Due to having simpler parsing rules, looking more like syntax, and that they can be used for more constructs, it’s recommended to prefer asterisks.
remark-stringify
formats strong with asterisks
by default.
Pass strong: '_'
to always use underscores.
ok-asterisk.md
When configured with '*'
.
**Mercury**.
No messages.
not-ok-asterisk.md
When configured with '*'
.
__Mercury__.
1:1-1:12: Unexpected strong marker `_`, expected `*`
ok-underscore.md
When configured with '_'
.
__Mercury__.
No messages.
not-ok-underscore.md
When configured with '_'
.
**Mercury**.
1:1-1:12: Unexpected strong marker `*`, expected `_`
not-ok-consistent.md
**Mercury** and __Venus__.
1:17-1:26: Unexpected strong marker `_`, expected `*`
not-ok.md
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-strong-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.
© 2010 - cnpmjs.org x YWFE | Home | YWFE