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

p1tools

v0.2.0

Published

Program 1 Tool Pack developed using Gluegun

Readme

💻 Pre requisites

You must have the VTEX CLI installed on your computer. To install, simply follow the step-by-step instructions provided by VTEX HERE

📦 How to install

To install, simply use the npm package manager by executing the command below:

    npm i p1tools

🎮 Commands

map-apps

Maps in which VTEX accounts the informed applications are installed

    p1tools map-apps

An entry will be requested with the accounts that will be verified and must be entered separated by commas (",") e.g.:

    ? Accounts (separated by ",") » account1,account2,...

Then you will be asked for an input with the apps that were searched for, the input must be the name of the apps separated by a comma (",") e.g.:

[!WARNING] The name of the app is what is in the name field of the manifest.json file within the repository

[!TIP] As it is analyzed by comparison, it is also possible to place the name of the account that the app was published in front of the app name, e.g. account1.app1

    ? Name of apps (separated by ",") » app1,app2,...

Then the application will log into each account (if necessary, it will request login, as is commonly done when using the VTEX CLI) and check whether the app is installed or whether it is in the edition, separating the return as follows:


Editions Apps
┌─────────┬──────────────┬──────────┐
│  App    │  Account     │  Exist?  │
├─────────┼──────────────┼──────────┤
│  app1   │  account1    │  ❌      │
├─────────┼──────────────┼──────────┤
│  app1   │  account2    │  ❌      │
└─────────┴──────────────┴──────────┘
Installed Apps
┌─────────┬──────────────┬──────────┐
│  App    │  Account     │  Exist?  │
├─────────┼──────────────┼──────────┤
│  app1   │  account1    │  ✅      │
├─────────┼──────────────┼──────────┤
│  app2   │  account2    │  ✅      │
└─────────┴──────────────┴──────────┘

update-accounts

Log into each VTEX account entered and perform a "vtex update"

    p1tools update-accounts

An entry will be input with the accounts that will be executed and must be entered separated by commas (",") e.g.:

    ? Accounts (separated by ",") » account1,account2,...

It will be executed account by account showing the progress.

Example:

√ Accounts (separated by ",") · account1,account2,account3
ℹ account1 ✅
ℹ account2 ✅
ℹ account3 ✅
✔ Running

🚀 Customizing your CLI

Check out the documentation at https://github.com/infinitered/gluegun/tree/master/docs.

🚀 Publishing to NPM

To package your CLI up for NPM, do this:

$ npm login
$ npm whoami
$ npm test

$ npm run build

$ npm publish

License

MIT - see LICENSE