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 🙏

© 2024 – Pkg Stats / Ryan Hefner

meta-npm

v1.2.7

Published

npm plugin for meta

Downloads

1,035

Readme

Build Status

meta-npm

npm plugin for meta

Using meta npm link && meta npm link --all enables a lerna-like experience for local development by creating symlinks so each project uses the development version of any other project in the meta repo:

For example, meta itself is developed in this way:

# install meta
npm i -g meta

# clone and enter the meta repo
meta git clone [email protected]:mateodelnorte/meta.git
cd ./meta

# install plugins
npm install

# run install for all child repos
meta npm install

# create symlinks to/from all child repos
meta npm link --all

# link meta itself globally
npm link

Usage

➜  meta npm

  Usage: meta-npm [options] [command]

  Options:

    -h, --help    output usage information

  Commands:

    clean         delete the node_modules folder in meta and child repositories
    install       npm install meta and child repositories
    link [--all]  npm link child repositories where used within child and meta repositories
    outdated      check outdated dependencies in meta and child repositories
    publish       npm publish meta and child repositories
    run           npm run commands against meta and child repositories
    symlink       directly symlink meta and child repositories without using global npm link
    help [cmd]    display help for [cmd]