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

@coding-with-hassan/lint-staged-config

v0.1.0

Published

Project-aware lint-staged config for monorepos with a NestJS API and an Angular SPA side by side.

Downloads

103

Readme

@coding-with-hassan/lint-staged-config

Project-aware lint-staged config factory. Designed for monorepos where a NestJS API and an Angular SPA live in sibling folders at the repo root.

Install

pnpm add -D @coding-with-hassan/lint-staged-config lint-staged

Use

Create lint-staged.config.js at the repo root:

module.exports = require('@coding-with-hassan/lint-staged-config')({
  api: 'de-autozaak-car-rental',
  spa: 'de-autozaak-car-rental-spa',
});

Both keys are optional — omit one if your repo only has the other side.

What it does

For the API folder:

  • *.ts → run ESLint with --fix --cache, scoped to that project (pnpm -C <dir>)

For the SPA folder:

  • *.ts, *.html → run Prettier --write then ESLint --fix --cache, scoped to that project
  • *.scss, *.css, *.json → run Prettier --write, scoped to that project

Per-project scoping means each side uses its own ESLint/Prettier config, so backend conventions don't leak into the frontend or vice versa.