Skip to documentation
ALEXANDRONET

package

@stackline/vfile-message 1.0.2 — installation and API

vfile utility to create a virtual message

Install @stackline/vfile-message

npm install @stackline/[email protected]

Package version: 1.0.2. Metadata verified: 2026-11-12. This is separate from the framework version and demonstration runtime.

Node.js requirement
{}
Accepted peer dependencies (declared ranges)
{}

Tested environments are described in the versioned README and linked source checks. A declared peer range is not evidence that every version in it was tested.

Versioned reference

This reference comes from the published @stackline/[email protected] README. Its upstream attribution and license remain with the source. Benchmark and security statements describe the cited tests and advisories, not a guarantee for every application.

@stackline/vfile-message

vfile utility to create a virtual message.

Documentation | npm | Issues | Repository

Current package version: 1.0.2

Why this package?

@stackline/vfile-message is the Stackline-maintained distribution of [email protected]. It is an independent continuation of vfile-message; original authors and licenses remain credited below.

Compatibility

Item Value
Package @stackline/[email protected]
API target [email protected]
Supported Node.js See supported framework requirements
License MIT
Module type module
Main entry index.js
Types index.d.ts
Runtime dependencies @types/unist, unist-util-stringify-position

Installation

npm install @stackline/vfile-message

Preserve existing imports and plugin resolution with an npm alias:

npm install vfile-message@npm:@stackline/vfile-message

Usage and API reference

vfile-message

Create vfile messages.

Contents

What is this?

This package provides a (lint) message format.

When should I use this?

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.

Install

This package is ESM only. In Node.js (version 14.14+ and 16.0+), install with npm:

npm install @stackline/vfile-message

In Deno with esm.sh:

import {VFileMessage} from 'https://esm.sh/vfile-message@3'

In browsers with esm.sh:

<script type="module">
  import {VFileMessage} from 'https://esm.sh/vfile-message@3?bundle'
</script>

Use

import {VFileMessage} from '@stackline/vfile-message'

const message = new VFileMessage(
  'Unexpected unknown word `braavo`, did you mean `bravo`?',
  {line: 1, column: 8},
  'spell:typo'
)

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,
  source: 'spell',
  ruleId: 'typo',
  position: {start: {line: 1, column: 8}, end: {line: null, column: null}}
}

API

This package exports the identifier VFileMessage. There is no default export.

VFileMessage(reason[, place][, origin])

Create a message for reason at place from origin.

When an error is passed in as reason, the stack is copied.

Parameters
  • reason (string or Error) — reason for message, uses the stack and message of the error if given
  • place (Node, Position, or Point, optional) — place in file where the message occurred
  • origin (string, optional) — place in code where the message originates (example: 'my-package:my-rule' or 'my-rule')
Extends

Error.

Returns

Instance of VFileMessage.

Fields
  • reason (string) — reason for message (you should use markdown)
  • fatal (boolean | null | undefined) — state of problem; true marks associated file as no longer processable (error); false necessitates a (potential) change (warning); null | undefined for things that might not need changing (info)
  • line (number | null) — starting line of error
  • column (number | null) — starting column of error
  • position (Position | null) — full unist position
  • source (string | null, example: 'my-package') — namespace of message
  • ruleId (string | null, example: 'my-rule') — category of message
  • stack (string | null) — stack of message in code
  • file (string | null) — path of a file (used throughout the VFile ecosystem)

Well-known

It’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.

Fields
  • actual (string | null) — specify the source value that’s being reported, which is deemed incorrect
  • expected (Array<string> | null) — suggest acceptable values that can be used instead of actual
  • url (string | null) — link to docs for the message (this must be an absolute URL that can be passed as x to new URL(x))
  • note (string | null) — long form description of the message (you should use markdown)

Types

This package is fully typed with TypeScript. It exports no additional types.

Compatibility

Projects maintained by the unified collective are compatible with all maintained versions of Node.js. As of now, that is Node.js 14.14+ and 16.0+. Our projects sometimes work with older versions, but this is not guaranteed.

Contribute

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.

License

MIT © Titus Wormer

Credits and original authors

Original copyright, license notices and contributor acknowledgements remain part of this distribution. Stackline maintenance does not replace authorship of the original work.

Use this repository's issue tracker for reproducible bugs and feature requests. Join r/Stackline for examples, usage questions and release discussions.