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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@rap2hpoutre/sync-yarn-lock

v1.0.2

Published

Sync package.json versions with yarn.lock - Modern replacement for syncyarnlock, supporting Yarn 4

Readme

sync-yarn-lock

npm version npm downloads license node

🔒 Sync your package.json versions with yarn.lock — Modern replacement for syncyarnlock, built for Yarn 4 (Berry)

Why?

When you run yarn add or yarn upgrade, Yarn updates your yarn.lock with exact versions, but leaves package.json with version ranges (like ^1.0.0). This can cause confusion about what's actually installed.

sync-yarn-lock updates your package.json to reflect the exact versions from your lockfile, making your dependencies explicit and reproducible.

vs. syncyarnlock

| Feature | sync-yarn-lock | syncyarnlock | | ------------------------ | -------------- | --------------------- | | Yarn 4 (Berry) support | ✅ | ❌ | | Yarn 1 (Classic) support | ❌ | ✅ | | Actively maintained | ✅ | ❌ (last update 2019) | | Zero dependencies | ✅ | ❌ | | Dry-run mode | ✅ | ❌ |

Installation

Using npx (recommended)

npx @rap2hpoutre/sync-yarn-lock

Global installation

npm install -g @rap2hpoutre/sync-yarn-lock
# or
yarn global add @rap2hpoutre/sync-yarn-lock

Usage

# Sync versions (modifies package.json)
npx @rap2hpoutre/sync-yarn-lock

# Preview changes without modifying files
npx @rap2hpoutre/sync-yarn-lock --dry-run

# Silent mode (only show errors)
npx @rap2hpoutre/sync-yarn-lock --silent

Options

| Option | Alias | Description | | ----------- | ----- | ------------------------------ | | --help | -h | Show help message | | --version | -v | Show version number | | --dry-run | -d | Preview changes without saving | | --silent | -s | Only output errors |

Example

Before:

{
  "dependencies": {
    "react": "^18.0.0",
    "react-dom": "^18.0.0"
  }
}

After running npx sync-yarn-lock:

{
  "dependencies": {
    "react": "18.2.0",
    "react-dom": "18.2.0"
  }
}

How it works

  1. Reads your package.json dependencies
  2. For each dependency, queries yarn info <package> --json to get the resolved version from yarn.lock
  3. Updates package.json with the exact versions
  4. Reports all changes made

Requirements

  • Node.js >= 18
  • Yarn 4 (Berry) - must be available in PATH

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT © rap2hpoutre