npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

vsource

v1.0.0

Published

Add messages to a vfile bound to a plugin source

Readme

vsource

Add messages to a vfile bound to a plugin source.

npm status node Test JavaScript Style Guide

Usage

const vsource = require('vsource')
const vfile = require('vfile')

const file = vfile({ path: 'package.json' })
const s = vsource('my-lint-plugin', file)

// Add error message to file
s.fail('Name must be lowercase', pos, 'lowercase-name')

Which is just a convenient shortcut for:

file.fail('Name must be lowercase', pos, 'my-lint-plugin:lowercase-name')

In addition, fail() can be called multiple times to collect more than one error, unlike VFile#fail() which immediately terminates the process. I'm taking a slightly different approach to linting (than remark-lint et al): both error and warning messages are lint failures, but warnings can be ignored by the user. This behavior is closer to the standard linter. While remark-lint normally only produces warning messages, reserving error messages for unexpected exceptions.

API

s = vsource(source[, file])

If a file argument is provided, it does not have to be passed into the below methods.

message = s.fail([file, ]reason, position, ruleId)

Add error message to file, similar to VFile#fail(). Sets message.fatal to true.

message = s.warn([file, ]reason, position, ruleId)

Add warning message to file, same as VFile#message(). Sets message.fatal to false.

message = s.info([file, ]reason, position, ruleId)

Add info message to file, same as VFile#info(). Sets message.fatal to null.

Install

With npm do:

npm install vsource

License

MIT © Vincent Weevers