Security News
vlt Debuts New JavaScript Package Manager and Serverless Registry at NodeConf EU
vlt introduced its new package manager and a serverless registry this week, innovating in a space where npm has stagnated.
remark-lint-link-title-style
Advanced tools
remark-lint rule to warn when link and definition titles occur with incorrect quotes
remark-lint
rule to warn when link title markers violate a given style.
This package checks the style of link (and image and definition) title markers.
You can use this package to check that the style of link title markers 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-link-title-style
In Deno with esm.sh
:
import remarkLintLinkTitleStyle from 'https://esm.sh/remark-lint-link-title-style@4'
In browsers with esm.sh
:
<script type="module">
import remarkLintLinkTitleStyle from 'https://esm.sh/remark-lint-link-title-style@4?bundle'
</script>
On the API:
import remarkLint from 'remark-lint'
import remarkLintLinkTitleStyle from 'remark-lint-link-title-style'
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(remarkLintLinkTitleStyle)
.use(remarkStringify)
.process(file)
console.error(reporter(file))
On the CLI:
remark --frail --use remark-lint --use remark-lint-link-title-style .
On the CLI in a config file (here a package.json
):
…
"remarkConfig": {
"plugins": [
…
"remark-lint",
+ "remark-lint-link-title-style",
…
]
}
…
This package exports no identifiers.
It exports the TypeScript types
Options
and
Style
.
The default export is
remarkLintLinkTitleStyle
.
unified().use(remarkLintLinkTitleStyle[, options])
Warn when link title markers violate a given style.
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).
type Options = Style | 'consistent'
Style
Style (TypeScript type).
type Style = '"' | '\'' | '()'
Before CommonMark, parens for titles were not supported in markdown.
They should now work in most places.
Parens do look a bit weird as they’re inside more parens:
[text](url (title))
.
In HTML, attributes are commonly written with double quotes.
Due to this, titles are almost exclusively wrapped in double quotes in
markdown, so it’s recommended to configure this rule with '"'
.
remark-stringify
formats titles with double
quotes by default.
Pass quote: "'"
to use single quotes.
There is no option to use parens.
ok-consistent.md
[Mercury](http://example.com/mercury/),
[Venus](http://example.com/venus/ "Go to Venus"), and
![Earth](http://example.com/earth/ "Go to Earth").
[Mars]: http://example.com/mars/ "Go to Mars"
No messages.
not-ok-consistent.md
[Mercury](http://example.com/mercury/ "Go to Mercury") and
![Venus](http://example.com/venus/ 'Go to Venus').
[Earth]: http://example.com/earth/ (Go to Earth)
2:1-2:50: Unexpected title markers `'`, expected `"`
4:1-4:49: Unexpected title markers `'('` and `')'`, expected `"`
ok-double.md
When configured with '"'
.
[Mercury](http://example.com/mercury/ "Go to Mercury").
No messages.
not-ok-double.md
When configured with '"'
.
[Mercury](http://example.com/mercury/ 'Go to Mercury').
1:1-1:55: Unexpected title markers `'`, expected `"`
ok-single.md
When configured with "'"
.
[Mercury](http://example.com/mercury/ 'Go to Mercury').
No messages.
not-ok-single.md
When configured with "'"
.
[Mercury](http://example.com/mercury/ "Go to Mercury").
1:1-1:55: Unexpected title markers `"`, expected `'`
ok-paren.md
When configured with '()'
.
[Mercury](http://example.com/mercury/ (Go to Mercury)).
No messages.
not-ok-paren.md
When configured with '()'
.
[Mercury](http://example.com/mercury/ "Go to Mercury").
1:1-1:55: Unexpected title markers `"`, expected `'('` and `')'`
not-ok.md
When configured with '🌍'
.
1:1: Unexpected value `🌍` for `options`, expected `'"'`, `"'"`, `'()'`, or `'consistent'`
ok-parens-in-url.md
When configured with '"'
.
Parens in URLs work correctly:
[Mercury](http://example.com/(mercury) "Go to Mercury") and
[Venus](http://example.com/(venus)).
No messages.
ok-whitespace.md
When configured with '"'
.
Trailing whitespace works correctly:
[Mercury](http://example.com/mercury/␠"Go to Mercury"␠).
No messages.
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-link-title-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.
FAQs
remark-lint rule to warn when link and definition titles occur with incorrect quotes
We found that remark-lint-link-title-style 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
vlt introduced its new package manager and a serverless registry this week, innovating in a space where npm has stagnated.
Security News
Research
The Socket Research Team uncovered a malicious Python package typosquatting the popular 'fabric' SSH library, silently exfiltrating AWS credentials from unsuspecting developers.
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.