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

@itrocks/webstorm

v0.3.3

Published

Facilitates developments on the it.rocks framework's source code within a single WebStorm project

Readme

npm version npm downloads GitHub issues discord

webstorm

Facilitates development on the it.rocks framework within a single WebStorm project.

These CLI tools allow you to work on @itrocks/* modules from sources inside a single app, with Git checkout + local builds and a watcher that rebuilds dependencies as you edit.

Requirements

  • Node.js ≥ 18
  • An application depending on one or more @itrocks/* packages under node_modules/@itrocks.

Installation

npm i --save-dev @itrocks/webstorm

Run via npx, or declare project scripts.

Commands

npx check-majors [upgrade]

Checks available major version updates for all @itrocks/* modules inside your project.

What it does:

  • Scans installed @itrocks/* packages.
  • Queries npm for newer major / minor / patch versions.
  • Prints a summary:
module-a    1.x → 2.x  available
module-b    up-to-date
  • If the upgrade argument is passed: upgrades version numbers, without installing anything.

Example:

npx check-majors upgrade

Output will clearly show the changes:

module-a   updated: 1.2.3 → 2.0.0
module-b   updated: 3.4.1 → 3.6.0
module-c   unchanged

The package.json files are modified to get the new version numbers.

Notes:

  • Requires vcs-modules to be run first in order to update the source Git repositories.
  • Does not install anything.
  • Useful before and to make a mass upgrade.
  • Works well together with npx it-publish and large Git commits directly from your WebStorm IDE.

npx it-publish

Publishes local @itrocks/* packages whose local version is ahead of npm.

What it does:

  • Compares local vs published version using:
    • if the package is not found in the search index → treated as not yet published;
    • if local version is greater than published → update will be published;
    • otherwise → reported as unchanged.
  • Runs npm publish (or npm publish --access public for packages not yet in the index) in each package directory.

At the end, it prints how many @itrocks packages were checked.

Dry-run: --dry

Add --dry to see exactly what would be published, without touching npm.

npx it-publish --dry

In this mode, the command only prints the intended npm publish calls:

Notes

  • Does not change any package.json.
  • Does not build your modules.
  • Uses the npm search index; very new publications might briefly appear as "not yet published" or "unchanged".

npx vcs-modules

Replaces any @itrocks/* package installed from npm with its Git repository checkout, builds it locally, and updates WebStorm configuration so the IDE recognises each module as a proper project.

What it does:

  • Scans node_modules/@itrocks/* in your app.
  • Updates WebStorm configuration file .idea/vcs.xml that each @itrocks/* module appears as a distinct Git root and project module inside WebStorm.
  • For each module that’s not already a Git checkout, removes the package folder and replaces it with the repository sources, so you can edit them.
  • Runs the module’s build if a build script exists in its package.json.
  • Builds modules in dependency order so shared libraries are ready before dependent ones.

Notes:

  • Requires each @itrocks/* module to have a build script.
  • Safe to run multiple times: it will only rebuild or update modules as needed.
  • Intended for local development, not CI.

npx wsbuild

Watches all @itrocks/* modules for file changes and rebuild them automatically.

What it does:

  • Watches all .ts and .scss source files under node_modules/@itrocks/**.
  • On change: detects the modified module, runs its npm run build script.

Notes:

  • Perfect for editing multiple @itrocks/* modules at once in a single environment.
  • Your app rebuilds itself using the freshly compiled outputs.
  • The build status is displayed in the console.
  • Debounces rapid edits to avoid overlapping builds.

Recommended setup

Add those commands to your package.json scripts for convenience:

{
  "scripts": {
    "itrocks:check": "check-majors",
    "itrocks:publish": "it-publish",
    "itrocks:setup": "vcs-modules",
    "itrocks:watch": "wsbuild"
  }
}

Then run:

npm run itrocks:check
npm run itrocks:publish
npm run itrocks:setup
npm run itrocks:watch

Troubleshooting

| Symptom | Cause / Fix | |----------------------------------|---------------------------------------------------------------| | No build script for a module | Add "build": "tsc" (or similar) in its package.json. | | Changes don’t reflect in the app | Ensure wsbuild is running and outputs are used by your app. | | Watcher does nothing | Edit files inside node_modules/@itrocks/<module>/src. | | Command not found | Run npm rebuild @itrocks/webstorm to restore links. |