vfile-message is a utility that creates vfile messages, using a (lint) message format with fields like line and column, ruleId, and source. It is useful when you need to emit warnings or errors even when you do not have a vfile-backed file object.
Project status
- Actively maintained: Yes, there is a recent upstream push and an npm update on 2025-07-26 (version 4.0.3), but after that there have been no further updates through 2026-06-09.
- Update cadence: The history shows infrequent updates, with a long gap between 2024-era none and the last known push, including a multi-year gap between 4.0.1/4.0.2 (2023) and 4.0.3 (2025). Current cadence appears low.
AI summary generated
Recent updates
4.0.3
Release 4.0.3 is described as a small internal refactor to support TypeScript 7. The code diff shows mostly maintenance changes, but there is also a runtime-visible change to how `VFileMessage` initializes some instance fields.
4.0.2
Release 4.0.2 updates TypeScript-related typings and build configuration, along with dependency version bumps. The release notes only mention updating @types/unist, but the code diff shows additional major dependency upgrades and tsconfig target/lib changes that could affect runtime behavior and/or generated type definitions.
Breaking4.0.1
Release 4.0.1 is a small packaging fix. It adds the missing `files` field to `package.json` so the intended build and type artifacts are included in the published npm package.
4.0.0
vfile-message 4.0.0 is a major release that formalizes a new `VFileMessage(reason[, options])` API, changes message location handling from `position` to `place`, and switches nullable fields from `null` to `undefined`. It also updates packaging to use an `exports` map and requires Node.js 16.
BreakingFeatures3.1.4
Release 3.1.4 is described in the notes as documentation improvements and a code-style refactor. The actual diff shows a structural change to the package entry implementation, plus related build/test configuration updates.
3.1.3
vfile-message 3.1.3 adds support for passing a VFileMessage instance as the `reason` argument to `new VFileMessage(reason, place, origin)`. The release notes also mention improved documentation, and the diff shows broader doc updates plus some tooling, test, and CI configuration changes.
Features3.1.2
Release 3.1.2 is a small patch focused on TypeScript/JSDoc typing. It updates the `VFileMessage` type definitions to again accept `Node` instances (from `unist`) as the `place` argument.
3.1.1
Release 3.1.1 is a small patch primarily focused on TypeScript typing adjustments for vfile-message. The code diff also includes several repository and tooling configuration changes, plus minor test robustness tweaks.
3.1.0
Release 3.1.0 introduces the well known `actual` and `expected` fields on `VFileMessage`, aligning the API with common message semantics (source value vs suggested/acceptable values). The README and inline JSDoc were updated to document these new properties.
Features3.0.2
Release 3.0.2 makes vfile-message more robust when creating a VFileMessage from a Node-like value that does not have a position field. The primary code change prevents position assignment when place.position is missing, and the test suite was updated to cover this scenario.