Gathering detailed insights and metrics for remark-lint-rule-style
Gathering detailed insights and metrics for remark-lint-rule-style
Gathering detailed insights and metrics for remark-lint-rule-style
Gathering detailed insights and metrics for remark-lint-rule-style
remark-lint-heading-style
remark-lint rule to warn when heading style violates the given style
remark-lint-ordered-list-marker-style
remark-lint rule to warn when the markers of ordered lists violate a given style
remark-lint-code-block-style
remark-lint rule to warn when code blocks do not adhere to a given style
remark-lint-link-title-style
remark-lint rule to warn when link and definition titles occur with incorrect quotes
npm install remark-lint-rule-style
Typescript
Module System
Node Version
NPM Version
remark-lint-no-unused-definitions@4.0.2
Updated on Apr 10, 2025
remark-lint-fenced-code-flag@4.2.0
Updated on Apr 09, 2025
remark-lint-no-undefined-references@5.0.2
Updated on Apr 09, 2025
10.0.1
Updated on Jan 27, 2025
remark-lint-table-cell-padding@5.1.0
Updated on Jan 27, 2025
remark-lint-table-pipe-alignment@4.1.0
Updated on Jan 27, 2025
JavaScript (100%)
Total Downloads
0
Last Day
0
Last Week
0
Last Month
0
Last Year
0
MIT License
987 Stars
629 Commits
135 Forks
19 Watchers
1 Branches
55 Contributors
Updated on Jul 13, 2025
Latest Version
4.0.1
Package Id
remark-lint-rule-style@4.0.1
Unpacked Size
14.37 kB
Size
4.45 kB
File Count
5
NPM Version
11.0.0
Node Version
23.1.0
Published on
Jan 27, 2025
Cumulative downloads
Total Downloads
Last Day
0%
NaN
Compared to previous day
Last Week
0%
NaN
Compared to previous week
Last Month
0%
NaN
Compared to previous month
Last Year
0%
NaN
Compared to previous year
remark-lint
rule to warn when thematic breaks (horizontal rules) are
inconsistent.
This package checks markers and whitespace of thematic rules.
You can use this package to check that thematic breaks 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:
1npm install remark-lint-rule-style
In Deno with esm.sh
:
1import remarkLintRuleStyle from 'https://esm.sh/remark-lint-rule-style@4'
In browsers with esm.sh
:
1<script type="module"> 2 import remarkLintRuleStyle from 'https://esm.sh/remark-lint-rule-style@4?bundle' 3</script>
On the API:
1import remarkLint from 'remark-lint' 2import remarkLintRuleStyle from 'remark-lint-rule-style' 3import remarkParse from 'remark-parse' 4import remarkStringify from 'remark-stringify' 5import {read} from 'to-vfile' 6import {unified} from 'unified' 7import {reporter} from 'vfile-reporter' 8 9const file = await read('example.md') 10 11await unified() 12 .use(remarkParse) 13 .use(remarkLint) 14 .use(remarkLintRuleStyle) 15 .use(remarkStringify) 16 .process(file) 17 18console.error(reporter(file))
On the CLI:
1remark --frail --use remark-lint --use remark-lint-rule-style .
On the CLI in a config file (here a package.json
):
1 … 2 "remarkConfig": { 3 "plugins": [ 4 … 5 "remark-lint", 6+ "remark-lint-rule-style", 7 … 8 ] 9 } 10 …
This package exports no identifiers.
It exports the TypeScript type
Options
.
The default export is
remarkLintRuleStyle
.
unified().use(remarkLintRuleStyle[, options])
Warn when thematic breaks (horizontal rules) are inconsistent.
options
(Options
, default: 'consistent'
)
— preferred style or whether to detect the first style and warn for
further differencesTransform (Transformer
from unified
).
Options
Configuration (TypeScript type).
'consistent'
— detect the first used style and warn when further rules differstring
(example: '** * **'
, '___'
)
— thematic break to prefer1type Options = string | 'consistent'
Rules consist of a *
, -
, or _
character,
which occurs at least three times with nothing else except for arbitrary
spaces or tabs on a single line.
Using spaces, tabs, or more than three markers is unnecessary work to type
out.
As asterisks can be used as a marker for more markdown constructs,
it’s recommended to use that for rules (and lists, emphasis, strong) too.
So it’s recommended to pass '***'
.
remark-stringify
formats rules with ***
by
default.
There are three settings to control rules:
rule
(default: '*'
) — markerruleRepetition
(default: 3
) — repetitionsruleSpaces
(default: false
) — use spaces between markersok.md
1Two rules: 2 3* * * 4 5* * *
No messages.
ok.md
When configured with '_______'
.
1_______ 2 3_______
No messages.
not-ok.md
1*** 2 3* * *
13:1-3:6: Unexpected thematic rule `* * *`, expected `***`
not-ok.md
When configured with '🌍'
.
11:1: Unexpected value `🌍` for `options`, expected thematic rule 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-rule-style@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.
No vulnerabilities found.
Reason
no dangerous workflow patterns detected
Reason
no binaries found in the repo
Reason
license file detected
Details
Reason
0 existing vulnerabilities detected
Reason
security policy file detected
Details
Reason
0 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 0
Reason
Found 2/30 approved changesets -- score normalized to 0
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
project is not fuzzed
Details
Reason
branch protection not enabled on development/release branches
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2025-07-07
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More