|
|
1 年之前 | |
|---|---|---|
| .. | ||
| lib | 1 年之前 | |
| index.d.ts | 1 年之前 | |
| index.js | 1 年之前 | |
| license | 1 年之前 | |
| package.json | 1 年之前 | |
| readme.md | 1 年之前 | |
Create vfile messages.
This package provides a (lint) message format.
In most cases, you can use file.message from VFile itself, but in some
cases you might not have a file, and still want to emit warnings or errors,
in which case this can be used directly.
This package is ESM only. In Node.js (version 16+), install with npm:
npm install vfile-message
In Deno with esm.sh:
import {VFileMessage} from 'https://esm.sh/vfile-message@4'
In browsers with esm.sh:
<script type="module">
import {VFileMessage} from 'https://esm.sh/vfile-message@4?bundle'
</script>
import {VFileMessage} from 'vfile-message'
const message = new VFileMessage(
'Unexpected unknown word `braavo`, did you mean `bravo`?',
{source: 'spell', ruleId: 'typo', place: {line: 1, column: 8}}
)
console.log(message)
Yields:
[1:8: Unexpected unknown word `braavo`, did you mean `bravo`?] {
reason: 'Unexpected unknown word `braavo`, did you mean `bravo`?',
line: 1,
column: 8,
ancestors: undefined,
cause: undefined,
fatal: undefined,
place: {line: 1, column: 8},
ruleId: 'typo',
source: 'spell'
}
This package exports the identifier VFileMessage.
There is no default export.
VFileMessage(reason[, options])Create a message for reason.
🪦 Note: also has obsolete signatures.
reason (string)
— reason for message (should use markdown)options (Options, optional)
— configuration.Instance of VFileMessage.
ancestors (Array<Node> or undefined)
— stack of (inclusive) ancestor nodes surrounding the messagecause (Error or undefined)
— original error cause of the messagecolumn (number or undefined)
— starting column of messagefatal (boolean or undefined)
— state of problem; true: error, file not usable; false: warning,
change may be needed; undefined: info, change likely not neededline (number or undefined)
— starting line of messageplace (Point, Position or undefined)
— place of messagereason (string)
— reason for message (should use markdown)ruleId (string or undefined, example: 'my-rule')
— category of messagesource (string or undefined, example: 'my-package')
— namespace of messageOptionsConfiguration (TypeScript type).
ancestors (Array<Node>, optional)
— stack of (inclusive) ancestor nodes surrounding the messagecause (Error, optional)
— original error cause of the messageplace (Point or Position, optional)
— place of messageruleId (string, optional, example: 'my-rule')
— category of messagesource (string, optional, , example: 'my-package')
— namespace of who sent the messageIt’s OK to store custom data directly on the VFileMessage, some of those are
handled by utilities.
The following fields are documented and typed here.
actual (string, optional)
— specify the source value that’s being reported, which is deemed incorrectexpected (Array<string>, optional)
— suggest acceptable values that can be used instead of actualurl (string, optional)
— link to docs for the message (this must be an absolute URL that can be
passed as x to new URL(x))note (string, optional)
— long form description of the message (you should use markdown)This package is fully typed with TypeScript.
It exports the additional type Options.
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, vfile-message@^4,
compatible with Node.js 16.
See contributing.md in vfile/.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.