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

winwsl

v0.0.3

Published

Keep separate node_modules trees for Windows and WSL in the same project.

Readme

winwsl

winwsl keeps separate node_modules trees for Windows and WSL inside the same project root, so switching environments does not force a full reinstall every time.

Install

npm i -g winwsl

Usage

Run it from a project directory that contains both package.json and package-lock.json:

winwsl
winwsl install
winwsl ci
winwsl run build

By default it stays quiet unless something fails. Use --verbose to see swap and restore details:

winwsl --verbose

Run install and ci through winwsl so it can track when one environment's cache is older than the current package.json and package-lock.json.

If you need to pass npm flags that collide with winwsl flags, insert -- first:

winwsl -- --version

How it works

  • node_modules is treated as the active tree for the current runtime.
  • node_modules_win stores the Windows dependency tree.
  • node_modules_wsl stores the WSL dependency tree.
  • winwsl restores the matching cache when it can, and falls back to a fresh install when it cannot.
  • A .winwslenv marker is written so future runs can tell which environment produced a given tree.

Requirements

  • Windows or WSL only
  • Node.js 20+
  • A valid package.json and package-lock.json in the current working directory