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

@marcin14092021/ghactions-playground

v1.0.1

Published

Przykladowy projekt do nauki pisania workflow GitHub Actions od zera

Readme

ghactions-playground

Prosty projekt Node.js do nauki pisania workflow GitHub Actions od zera.

Co jest w projekcie

  • src/math.js — kilka prostych funkcji (add, subtract, divide)
  • src/math.test.js — testy jednostkowe (Jest)
  • eslint.config.js — konfiguracja lintera

Uruchamianie lokalnie

npm install
npm test
npm run lint

Cel: napisz workflow GitHub Actions od zera

Ten projekt celowo nie zawiera pliku .github/workflows/*.yml — to Twoje zadanie.

Stwórz plik .github/workflows/ci.yml, który przy każdym push i pull_request:

  1. Checkout kodu repozytorium
  2. Instaluje Node.js (np. wersja 20)
  3. Instaluje zależności (npm install lub npm ci)
  4. Uruchamia lint (npm run lint)
  5. Uruchamia testy (npm test)

Kolejne kroki do samodzielnego eksperymentowania

  • Dodaj matrix i przetestuj na kilku wersjach Node (np. 18, 20, 22)
  • Dodaj cache dla node_modules (actions/cache lub wbudowany cache w actions/setup-node)
  • Rozdziel lint i testy na osobne joby działające równolegle
  • Dodaj krok, który celowo zepsuje test lub lint, i zobacz jak wygląda czerwony status w zakładce Actions
  • Dodaj if: failure() z krokiem, który coś wypisze, gdy pipeline się nie powiedzie
  • Spróbuj triggera workflow_dispatch, żeby uruchamiać pipeline ręcznie