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 🙏

© 2024 – Pkg Stats / Ryan Hefner

one-version

v0.2.0

Published

A strict dependency conformance tool for (mono)repos!

Downloads

117

Readme

one-version

A strict dependency conformance tool for (mono)repos!

Docs

Getting Started:

Install one-version from the root of your repo (even for monorepos!):

bun add one-version

Add a one-version:check script to your root package.json:

{
  "scripts": {
    "one-version:check": "one-version check"
  }
}

Configuration:

one-version can be configured using a one-version.config.(jsonc|json) file in the root of your repo. Here's an example:

{
  "$schema": "https://one-version.vercel.app/schema.json",
  // one of: "bun", "yarn-berry", "yarn-classic", "pnpm", "npm"
  // by default it will try to detect the package manager based on the presence of a lockfile
  "packageManager": "bun",
  // A mapping of dependencies, and which workspaces are "allowed" to use different versions
  "overrides": {
    "react": {
      "18.0.0": ["pkg-a"],
      // Wildcards are supported, and will capture any workspaces!
      "17.0.0": ["*"]
    }
  },
  // one of: "pin", "loose", defaults to `loose` if not provided
  // pin: all dependencies and devDependencies must use an exact version
  // meaning no ranges (`^`, `~`, `.x`, etc.) are allowed
  "versionStrategy": "pin"
}

Supported Package Managers/Versions:

  • Bun (bun)
  • Yarn Berry (yarn-berry) - Yarn versions 2.x, 3.x, 4.x
  • Yarn Classic (yarn-classic) - Yarn versions 1.x
  • PNPM (pnpm)
  • NPM (npm) - npm versions 7.x and greater

Inspiration:

This is effectively a fork of the wayfair/one-version project, which I had partially contributed to while I was at Wayfair. This fork is intended to be a slimmer re-write of the original project, aiming to support the same functionality (eventually)!

This tool should be a drop-in replacement for @wayfair/one-version, if you run into any issues or collisions, please open an issue!

This package also notably includes a few additional features:

  • Support for npm and bun package managers
  • Support for wildcards ("*") within the overrides configuration
  • Support for "versionStrategy" configuration to enforce strict versioning across the repo!

Contributing:

This library does not have a build step currently.

Code Quality:

Type Checking:

This library uses TypeScript to perform type checks, run bun run type-check from the root or from this workspace!

Linting

This library uses BiomeJS for linting, run bun run lint from the root or from this workspace!

Tests

This library uses Node.js for running unit tests, run bun run test from the root or from this workspace!

Publishing:

To publish the library, run bun run pub from the workspace root. This will prompt you to login to npm and publish the package.