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

dtype-linter

v1.0.11

Published

A tiny, zero-dependency code-style checker for JavaScript

Readme

dtype-linter

A tiny, zero-dependency code-style checker for JavaScript.

dtype-linter scans the .js files in your project and reports common formatting issues that quietly hurt readability — overly long lines, trailing whitespace, mixed indentation and empty catch blocks. No config files, no plugins, no setup. Just run it.

Why another linter?

Full-featured linters are powerful but heavy: dozens of transitive dependencies, a config file to maintain and a learning curve. Sometimes you just want a fast, honest check that your code is tidy. dtype-linter does exactly that — and nothing more.

  • 🪶 Zero dependencies — a single small script
  • Instant — no config, no cache, no warm-up
  • 📁 Recursive — scans the current folder and subfolders (skips node_modules)
  • 🎯 Clear output — every issue as file:line
  • 🤖 CI-friendly — exits with code 1 when issues are found

Installation

npm install -g dtype-linter

Usage

Run it from the root of any project:

dtype-linter lint

Example output:

src/app.js:45  line longer than 100 characters
src/db.js:12  trailing whitespace
server.js:8  mixed tabs and spaces

Problems found: 3

When everything is clean:

Clean! No problems found.

The process exits with status 1 if any problems are found, so you can drop it straight into a CI pipeline or a pre-commit hook:

dtype-linter lint || echo "Please fix the issues above before committing."

Rules

| Rule | What it catches | |------|-----------------| | Line length | Lines longer than 100 characters | | Trailing whitespace | Spaces or tabs at the end of a line | | Mixed indentation | Lines that mix tabs and spaces | | Empty catch | catch {} blocks that silently swallow errors |

Notes

dtype-linter is intentionally minimal. It does not rewrite your code, it only reports. For deep static analysis and auto-fixing, reach for a full linter — for a quick tidiness check, this is all you need.

License

ISC