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

eslint-plugin-tsify

v1.1.0

Published

ESLint plugin for defining bunch of best TS practices for your project. For eg. one-interface-per-file will make sure you only have one interface defined for a single file reducing the chances of circular dependencies.

Readme

About

This is a custom ESLint plugin that enforces a bunch of best practices for TypeScript projects. For eg. one-interface-per-file will make sure you only have one interface defined for a single file reducing the chances of circular dependencies.

Usage

In your .eslintrc.json file, add the following in the plugins section:

"plugins": [
    ...
    "eslint-plugin-tsify"
],

In the rules section, add the rules you want to enforce.

"rules": {
    ...
    "tsify/one-interface-per-file": "error",
}

Rules

one-interface-per-file

Enforces that only one TypeScript interface is defined per file.

one-enum-per-file

Enforces that only one TypeScript enum is defined per file.

proper-semantics

Enforces that the TypeScript files are defined with proper semantics. For eg. an interface should be defined in a file with .interface.ts extension, a type should be defined in a file with .type.ts extension, an enum should be defined in a file with .enum.ts extension.