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

@whydrf/eslint-plugin-nava

v0.1.1

Published

An opinionated ESLint plugin for TypeScript projects that enforces clean code conventions, import organization, type safety patterns, and consistent module structure.

Readme

@whydrf/eslint-plugin-nava

An opinionated ESLint plugin for TypeScript projects that enforces clean code conventions, import organization, type safety patterns, and consistent module structure.

Features

Custom rules:

  • nava/no-inline-type-imports — Disallows import { type X } and enforces import type { X }. Also splits mixed imports (import { type X, Y }) into separate type/value imports. This rule works at the text level, so it reports and auto-fixes even though the TypeScript parser normalizes inline type imports.
  • nava/multiline-type-literals — Enforces that inline object type literals and interface bodies span multiple lines.
  • nava/module-member-order — Enforces top-level declarations to be ordered as imports -> enum -> type -> interface -> const.

Bundled configurations:

  • nava/recommended — registers the plugin rules plus @typescript-eslint/consistent-type-imports.
  • nava/react — a full flat config for React/TypeScript projects. It includes eslint-plugin-perfectionist (import sorting) and eslint-plugin-prettier, and is customizable (see below).

Installation

npm install --save-dev @whydrf/eslint-plugin-nava
# or
pnpm add -D @whydrf/eslint-plugin-nava

eslint and typescript-eslint are peer dependencies and must be installed in your project.

Usage

Recommended (rules only)

In your eslint.config.js / eslint.config.mjs:

import nava from '@whydrf/eslint-plugin-nava/recommended';

export default [
    nava,
    {
        rules: {
            // override any rule here
            'nava/no-inline-type-imports': 'warn',
        },
    },
];

Full React config

import navaReact from '@whydrf/eslint-plugin-nava/configs/react';

export default [
    ...navaReact,
    {
        rules: {
            // override any rule or add your own
            'perfectionist/sort-imports': [
                'error',
                {
                    groups: [['builtin', 'external'], ['alias'], ['parent', 'sibling', 'index'], 'unknown'],
                    customGroups: [
                        { elementNamePattern: '^@modules/', groupName: 'alias' },
                        { elementNamePattern: '^src/', groupName: 'sibling' },
                    ],
                    type: 'line-length',
                    newlinesBetween: 1,
                    order: 'desc',
                },
            ],
        },
    },
];

Single rule

import nava from '@whydrf/eslint-plugin-nava';

export default [
    {
        plugins: { nava },
        rules: {
            'nava/no-inline-type-imports': 'error',
            'nava/multiline-type-literals': 'error',
            'nava/module-member-order': 'error',
        },
    },
];

Rules

| Rule | Description | Fixable | | --- | --- | --- | | nava/no-inline-type-imports | Use import type { X } instead of import { type X } | ✅ | | nava/multiline-type-literals | Inline object type literals and interface bodies must be multiline | ✅ | | nava/module-member-order | Top-level declarations ordered as imports -> enum -> type -> interface -> const | ✅ |

License

MIT

Tips

  • Import the recommended config to enable all rules at once.

Migration

See docs/migration.md for moving from local rules.

FAQ

Why a custom no-inline-type-imports? The TypeScript parser normalizes inline type imports, so a standard rule cannot report them. This rule inspects raw text.

Contributing

See CONTRIBUTING.md.

Internal

Rules share a small sort helper in src/sort-utils.ts.

Status

  • v0.1.0: initial release

Status

  • v0.1.0: initial release

Internals

Rules share a small sort helper.

Contributing

See CONTRIBUTING.md for local setup.

Migration

See docs/migration.md to move from local rules.