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

@ziyadedher/eslint-config

v3.1.1

Published

πŸ› πŸš€ Ziyad's ESLint configuration for hypermodern web development (TypeScript + Next.js + TailwindCSS).

Readme

eslint-config-ziyad

πŸ› πŸš€ Ziyad's ESLint configuration for hypermodern web development (TypeScript + Next.js + TailwindCSS).

This is part of a larger effort to streamline the process of very quickly spinning up high-quality webapp projects (mostly for myself). A link to more information will eventually land here.

Philosophy

I really like Black's concept of an uncompromising Python code formatter. There are three major tenants of the philosophy this configuration follows:

  1. Eliminate the need to think about the minutiae of code style.
  2. Provide a universal, easy-to-follow style guide for new projects.
  3. Encourage the use of well-build modern technologies.

Rules

Check out the .eslintrc.yaml for the most up-to-date view of what rules and plugins are enabled.

Notably, this config does not introduce any new rules. It just configures existing ones.

Versioning

This projects follows a modified semantic versioning scheme for major, minor, and patch releases.

  • Major: a technology change (addition or removal), or otherwise completely backwards-incompatible change.
  • Minor: a rule or dependency change that may be backwards-incompatible and does not have an automated fix.
  • Patch: a rule or dependency change that is either backwards-compatible or has an automated fix.