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

update-scopes

v2.0.261

Published

## TLDR

Readme

Moving to @wix scopes

TLDR

We want to make all our private npm packages to be scoped. It means that, for example, instead of having wix-axios-config you should start using @wix/wix-axios-config. The update-scopes tool helps to migrate your code to use scoped packages.

Usage

Use our standalone CLI tool, with npx in each of your builds' root directory.

npx update-scopes

Or install it globally:

npm install -g update-scopes
update-scopes

What's happening?

This tool will change your code to use scoped packages (@wix). Your code will still use the private npm registry but will require the scoped packages. Since we already publish all packages both as scoped and non-scoped versions this should have no runtime effects on your application.

What to do if I run into problems?

If you experience any issues please contact us at #update-scopes.

What if I have a monorepo or an n-build 1 repo?

You can use the following script to migrate repos with multiple packages easier. The script runs recursively on all directories other than node_modules and runs the update-scopes script on any package it finds:

curl -L https://bit.ly/update-scopes-recursively | bash

It then creates a different commit for each sub-package.

What should I do if I am already using scoped packages?

Run the script anyway, you might have missed something. The script will detect that you're already using scoped packages and will not make any changes if none are needed.

Caveats

  1. The script will notify you if it finds any Wix packages names that it's not sure if it should migrate or not:
/var/folders/q4/y966_22s5q533wldcfdkdx0rwls4rs/T/us-Dj5Nt0/files-suspicious.txt

Check the contents of the file and migrate manually if needed.

  1. If you are exposing .d.ts files from a Javascript project this script will change all the declarations and this might result in duplicate declarations. Change them back manually if needed.

    An example of a .d.ts that needs to be fixed: https://github.com/wix-private/fed-infra/blob/7d33a851fec588263967b06b2ae79686fdcf1ff7/wix-axios-config/index.d.ts