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

angular-challenges

v0.2.0

Published

Start and submit Angular Challenges (https://angular-challenges.vercel.app) from your terminal: fork, clone, install, branch, serve and open a PR.

Readme

angular-challenges CLI

Try a challenge from Angular Challenges with one command:

npx angular-challenges start 19

This will:

  1. find your GitHub account (via the gh CLI if signed in, otherwise it asks),
  2. fork tomalaforge/angular-challenges to your account (or reuse your fork),
  3. ask where to clone your fork — default ./angular-challenges (or reuse an existing clone),
  4. create an answer-19 branch from the latest upstream main,
  5. run pnpm install,
  6. open the project in your editor (VS Code, Cursor, Windsurf or JetBrains), and
  7. serve the challenge app.

When your solution is ready:

npx angular-challenges submit

pushes your branch and opens a pre-filled pull request page (Answer:19).

Options

  • --dir <path> — clone location. Skips the question, so it also works in scripts: npx angular-challenges start 19 --dir ~/code. If the folder already has files in it, the clone goes into <path>/angular-challenges.

Requirements

  • Node.js ≥ 20 and git. pnpm is enabled automatically through corepack.
  • A GitHub account. The GitHub CLI is optional but makes forking seamless.

Publishing (maintainers)

cd cli && npm publish