remark-lint
rule to warn when tabs are used.
- What is this?
- When should I use this?
- Presets
- Install
- Use
- API
- Recommendation
- Fix
- Examples
- Compatibility
- Contribute
- License
This package checks for tabs.
You can use this package to check tabs.
This plugin is not included in presets maintained here.
This package is ESM only. In Node.js (version 16+), install with npm:
npm install remark-lint-no-tabs
In Deno with esm.sh
:
import remarkLintNoTabs from 'https://esm.sh/remark-lint-no-tabs@4'
In browsers with esm.sh
:
<script type="module">
import remarkLintNoTabs from 'https://esm.sh/remark-lint-no-tabs@4?bundle'
</script>
On the API:
import remarkLint from 'remark-lint'
import remarkLintNoTabs from 'remark-lint-no-tabs'
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(remarkLintNoTabs)
.use(remarkStringify)
.process(file)
console.error(reporter(file))
On the CLI:
remark --frail --use remark-lint --use remark-lint-no-tabs .
On the CLI in a config file (here a package.json
):
…
"remarkConfig": {
"plugins": [
…
"remark-lint",
+ "remark-lint-no-tabs",
…
]
}
…
This package exports no identifiers.
It exports no additional TypeScript types.
The default export is
remarkLintNoTabs
.
Warn when tabs are used.
There are no options.
Transform (Transformer
from unified
).
Regardless of the debate in other languages of whether to use tabs versus spaces, when it comes to markdown, tabs do not work as expected. Largely around things such as block quotes, lists, and indented code.
Take for example block quotes: >\ta
gives a paragraph with the text a
in a blockquote,
so one might expect that >\t\ta
results in indented code with the text a
in a block quote.
>\ta
>\t\ta
Yields:
<blockquote>
<p>a</p>
</blockquote>
<blockquote>
<pre><code> a
</code></pre>
</blockquote>
Because markdown uses a hardcoded tab size of 4,
the first tab could be represented as 3 spaces (because there’s a >
before).
One of those “spaces” is taken because block quotes allow the >
to be
followed by one space,
leaving 2 spaces.
The next tab can be represented as 4 spaces,
so together we have 6 spaces.
The indented code uses 4 spaces, so there are two spaces left, which are
shown in the indented code.
remark-stringify
uses spaces exclusively for indentation.
␠␠␠␠mercury()
No messages.
␉mercury()
Venus␉and Earth.
1:1: Unexpected tab (`\t`), expected spaces
3:6: Unexpected tab (`\t`), expected spaces
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-no-tabs@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.