Security News
JSR Working Group Kicks Off with Ambitious Roadmap and Plans for Open Governance
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
remark-lint-no-multiple-toplevel-headings
Advanced tools
remark-lint rule to warn when multiple top level headings are used
remark-lint
rule to warn when more than one top level heading is used.
This package is a unified (remark) plugin, specifically a remark-lint
rule.
Lint rules check markdown code style.
You can use this package to check that no more than one top level heading is used.
This rule is included in the following presets:
Preset | Setting |
---|---|
remark-preset-lint-markdown-style-guide |
This package is ESM only. In Node.js (version 12.20+, 14.14+, or 16.0+), install with npm:
npm install remark-lint-no-multiple-toplevel-headings
In Deno with esm.sh
:
import remarkLintNoMultipleToplevelHeadings from 'https://esm.sh/remark-lint-no-multiple-toplevel-headings@3'
In browsers with esm.sh
:
<script type="module">
import remarkLintNoMultipleToplevelHeadings from 'https://esm.sh/remark-lint-no-multiple-toplevel-headings@3?bundle'
</script>
On the API:
import {read} from 'to-vfile'
import {reporter} from 'vfile-reporter'
import {remark} from 'remark'
import remarkLint from 'remark-lint'
import remarkLintNoMultipleToplevelHeadings from 'remark-lint-no-multiple-toplevel-headings'
main()
async function main() {
const file = await remark()
.use(remarkLint)
.use(remarkLintNoMultipleToplevelHeadings)
.process(await read('example.md'))
console.error(reporter(file))
}
On the CLI:
remark --use remark-lint --use remark-lint-no-multiple-toplevel-headings example.md
On the CLI in a config file (here a package.json
):
…
"remarkConfig": {
"plugins": [
…
"remark-lint",
+ "remark-lint-no-multiple-toplevel-headings",
…
]
}
…
This package exports no identifiers.
The default export is remarkLintNoMultipleToplevelHeadings
.
unified().use(remarkLintNoMultipleToplevelHeadings[, config])
This rule supports standard configuration that all remark lint rules accept
(such as false
to turn it off or [1, options]
to configure it).
The following options (default: 1
) are accepted:
number
(example: 1
)
— assumed top level heading rankDocuments should almost always have one main heading, which is typically a
heading with a rank of 1
.
ok.md
When configured with 1
.
# Foo
## Bar
No messages.
not-ok.md
When configured with 1
.
# Foo
# Bar
3:1-3:6: Don’t use multiple top level headings (1:1)
Projects maintained by the unified collective are compatible with all maintained versions of Node.js. As of now, that is Node.js 12.20+, 14.14+, and 16.0+. Our projects sometimes work with older versions, but this is not guaranteed.
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.
FAQs
remark-lint rule to warn when multiple top level headings are used
The npm package remark-lint-no-multiple-toplevel-headings receives a total of 62,864 weekly downloads. As such, remark-lint-no-multiple-toplevel-headings popularity was classified as popular.
We found that remark-lint-no-multiple-toplevel-headings demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 3 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
At its inaugural meeting, the JSR Working Group outlined plans for an open governance model and a roadmap to enhance JavaScript package management.
Security News
Research
An advanced npm supply chain attack is leveraging Ethereum smart contracts for decentralized, persistent malware control, evading traditional defenses.
Security News
Research
Attackers are impersonating Sindre Sorhus on npm with a fake 'chalk-node' package containing a malicious backdoor to compromise developers' projects.