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

@versu/plugin-node

v1.0.4

Published

Versu Node.js Plugin

Downloads

475

Readme

versu

@versu/plugin-node - Node.js Adapter Plugin

Node.js adapter plugin for Versu. Provides support for detecting and updating versions in Node.js projects, including npm, yarn and pnpm workspace monorepos.

Installation

npm install @versu/core @versu/plugin-node

Usage

Once installed, the plugin is discovered automatically from node_modules (or list it explicitly in the plugins array of your versu.config.js):

import { VersuRunner } from '@versu/core';

const runner = new VersuRunner({
  repoRoot: '/path/to/repository',
  adapter: 'node', // Optional - auto-detected
  // ...other options as needed
});

const result = await runner.run();

Auto-Detection

The plugin automatically activates when package.json is present in the repository root.

Workspace Support

Workspace members are discovered from:

  • the workspaces field of the root package.json (npm / yarn, array or { packages: [] } form), or
  • pnpm-workspace.yaml (packages globs) when the root package.json declares no workspaces.

Projects without workspaces are handled as a single root module.

Dependencies between workspace packages (dependencies, devDependencies, peerDependencies, optionalDependencies) are used to build the dependency cascade: bumping a package also affects the packages that depend on it.

Notes

  • Module IDs follow Gradle-style notation (e.g., : for root, :packages:core).
  • The plugin updates:
    • the version field of a module's package.json when the module declares a version.
    • internal dependency ranges pointing at renumbered workspace packages, preserving the range operator and the workspace: protocol (e.g. ^1.2.3^2.0.0, workspace:~1.2.3workspace:~2.0.0).
  • Specs without a concrete version are left untouched: *, workspace:*, workspace:^, workspace:~, file:, link:, git/url specs and compound ranges.

📄 License

MIT License - see LICENSE for details.