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

@shoutem/cli

v0.16.4

Published

Command-line tools for Shoutem applications

Readme

Shoutem CLI

Shoutem CLI is a command line tool which helps you build Shoutem extensions.

You can read more about CLI in our documentation

Local Development

For local development there are three ways of approaching this:

1. Compiling and running from the repository

  1. Run npm i inside repository
  2. Run node path/to/build/shoutem.js <command>, where <command> is the command you're testing

After making changes to the code, you can run rm -rf build && npm run build to recompile and then continue using step 2 described above.

2. Editing global node_modules

While messy and harder to keep track of changes (since you can't see the diff directly), this has proven effective. You can make changes in your global node_modules directory on your machine in the src directory, then re-build the CLI using npm run build within the cli directory (where the package.json is).

3. Installing via git commit hash

Prerequisites:

  • babel-cli v6.8.0 installed globally on your machine
  • commit should have package.json edited in such a way that the prepare script is replaced with a preinstall script

You can see the changes you've made with your code and how they affect the CLI by using npm i -g shoutem/cli#<commit_hash>, e.g.: npm i -g shoutem/cli#6874qbr

This can also be used for testing before release, unlike the other two methods.

NOTE: Once a release is ready, make sure to turn the preinstall script back into a prepare script as users may not have babel-cli installed.