Installation

# Preserve existing imports with an npm alias
npm install vfile-sort@npm:@stackline/vfile-sort@1.0.2
# Or use the scoped package name in your imports
npm install @stackline/vfile-sort@1.0.2

Node.js: See compatibility notes. Read the compatibility and maintenance notes before migrating.

Usage and API

@stackline/vfile-sort

vfile utility to sort messages by line/column.

Documentation | npm | Issues | Repository

Current package version: 1.0.2

Why this package?

@stackline/vfile-sort is the Stackline-maintained distribution of vfile-sort@3.0.1. It is an independent continuation of vfile-sort; original authors and licenses remain credited below.

Compatibility

Installation

npm install @stackline/vfile-sort

Preserve existing imports and plugin resolution with an npm alias:

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

Usage and API reference

vfile-sort

vfile utility to sort messages.

Contents

• What is this?
• When should I use this?
• Install
• Use
• API
  • sort(file)
• Types
• Compatibility
• Contribute
• License

What is this?

This is a small package to sort the list of messages. It first sorts by line/column: earlier messages come first. When two messages occurr at the same place, sorts fatal error before warnings, before info messages. Finally, it sorts using localeCompare on source, ruleId, or finally reason.

When should I use this?

You can use this right before a reporter is used to give humans a coherent report.

Install

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

npm install @stackline/vfile-sort

In Deno with esm.sh:

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

In browsers with esm.sh:

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

Use

import {VFile} from 'vfile'
import {sort} from '@stackline/vfile-sort'

const file = VFile()

file.message('Error!', {line: 3, column: 1})
file.message('Another!', {line: 2, column: 2})

sort(file)

console.log(file.messages.map(d => String(d)))
// => ['2:2: Another!', '3:1: Error!']

API

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

sort(file)

Sort messages in the given vfile.

Parameters

• file (VFile) — file to sort

Returns

Sorted file (VFile).

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 project: vfile-sort.
• Titus Wormer.
• Copyright (c) 2015 Titus Wormer tituswormer@gmail.com.
• Stackline maintenance: Alexandro Paixao Marques and Stackline contributors.

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

Community and Links

• Stackline website
• GitHub projects
• npm packages
• Reddit community — r/Stackline
• Maintainer LinkedIn

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

Upstream issues and maintenance review

Upstream and maintenance review

This package maintains vfile-sort@3.0.1 under the independent @stackline/vfile-sort name.

• Source: https://github.com/vfile/vfile-sort/tree/4ac681c9c6e2629aad87c2366f9f9e9ea10f0e8d
• Public npm artifact integrity: sha512-1os1733XY6y0D5x0ugqSeaVJm9lYgj0j5qdcZQFyxlZOSy1jYarL77lLyb5gK4Wqr1d5OxmuyflSO3zKyFnTFw==.
• Upstream issue evidence checked: 2026-09-29T00:22:21.069158+00:00.
• Original license and author notices are retained.
• The upstream published runtime files and declarations are hash-checked in .stackline/upstream.json. Any runtime fix is explicitly listed there.
• Functional upstream suites run against the source and extracted final package. Development tools were reduced to those used by validation; full source and runtime audits must pass.
• Only direct dependencies of the original Stackline portfolio are in this migration. This is not a claim that all transitive projects are maintained by Stackline.

Issue triage

The queried open-issue list contained no issue entries. This does not establish that the upstream is abandoned or bug-free. No runtime bug fix is claimed for this initial maintenance release.

The evidence query fetched the latest 100 open and 30 closed issue/PR entries and removed PRs. Closed entries were collected for context; this report does not claim an exhaustive historic review.

Release discipline

The source commit, passing CI and CodeQL, reviewed CI tarball hash, npm provenance, normal and aliased installs, and immutable GitHub release are checked before a release is complete. Published versions and tags are never replaced.

Release changes

Changelog

1.0.0

• Start Stackline maintenance of the documented upstream API.
• Preserve and verify published runtime files and TypeScript declarations.
• Run upstream functional suites against both source and the final package.
• Publish the reviewed CI artifact through GitHub Actions with provenance and immutable release evidence.

Release files and references

• README.md
• UPSTREAM.md
• CHANGELOG.md
• NOTICE
• Package and publication metadata
• Full text documentation

Package bytes, npm provenance and the immutable GitHub release were verified for this version. Security checks describe the reviewed release; documented compatibility risks and upstream reports are not blanket claims of resolution.