Warn for literal URLs in text.
URLs are treated as links in some Markdown vendors, but not in others.
To make sure they are always linked, wrap them in <
(less than) and >
(greater than).
Fix
remark-stringify
never creates literal URLs and always uses <
(less than) and >
(greater than).
See Using remark to fix your Markdown
on how to automatically fix warnings for this rule.
Presets
This rule is included in the following presets:
Example
ok.md
In
<http://foo.bar/baz>
Out
No messages.
not-ok.md
In
Note: this example uses GFM.
http://foo.bar/baz
Out
1:1-1:19: Don’t use literal URLs without angle brackets
Install
This package is ESM only:
Node 12+ is needed to use it and it must be imported
ed instead of required
d.
npm:
npm install remark-lint-no-literal-urls
This package exports no identifiers.
The default export is remarkLintNoLiteralUrls
.
Use
You probably want to use it on the CLI through a config file:
…
"remarkConfig": {
"plugins": [
…
"lint",
+ "lint-no-literal-urls",
…
]
}
…
Or use it on the CLI directly
remark -u lint -u lint-no-literal-urls readme.md
Or use this on the API:
import {remark} from 'remark'
import {reporter} from 'vfile-reporter'
import remarkLint from 'remark-lint'
import remarkLintNoLiteralUrls from 'remark-lint-no-literal-urls'
remark()
.use(remarkLint)
+ .use(remarkLintNoLiteralUrls)
.process('_Emphasis_ and **importance**')
.then((file) => {
console.error(reporter(file))
})
Contribute
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.
License
MIT © Titus Wormer