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

@no-npm/cli

v0.2.10

Published

The not only NPM project helps you to run micro frontends directly from a npm package.

Downloads

14

Readme

noNPM cli

Run noNPM locally with:

npx @no-npm/cli

You can point noNPM to another registry:

npx @no-npm/cli --registry http://localhost:4111

All packages will be stored in the --storage folder which is by default .noNPM.

All options

You can run it with the --help flag to see all options of the cli:

Usage:  start [options]

Start the noNPM server.

Options:
  -p, --port <port>    Define the port to run at. (default: "3000")
  --storage <path>     The path where the packages are stored. (default: "./.noNPM")
  --registry <name>    Define the registry to use. Defaults to https://registry.npmjs.org/. (default: "https://registry.npmjs.org/")
  --serveAll           Serves all npm packages, even if they do not have a serve property set. (default: false)
  --defaultApp <name>  Define a application that is served via the base path. By default the @no-npm/web package is used. (default: "@no-npm/web")
  --cors               Set this to false, to disable cors (default: `true`). (default: true)
  --logging [log...]   Define the log-level. Possible values are: log,error,warn,debug,verbose (default: "log,error,warn,debug")
  -h, --help           display help for command