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

@flowpanel/eslint-plugin

v0.1.0

Published

ESLint rules for FlowPanel admin configs

Readme

@flowpanel/eslint-plugin

ESLint rules that catch the most common mistakes in FlowPanel admin configs.

Pre-1.0. The rule names are stable; the surface (options, message text) may still shift before 1.0.

Install

pnpm add -D @flowpanel/eslint-plugin

Setup (ESLint v9 flat config)

// eslint.config.ts
import flowpanel from "@flowpanel/eslint-plugin";

export default [
  {
    plugins: { flowpanel },
    rules: {
      "flowpanel/prefer-shorthand-filter": "warn",
      "flowpanel/audit-row-action-needs-confirm": "error",
      "flowpanel/no-server-import-in-client": "error",
      "flowpanel/require-unique-resource-names": "error",
      "flowpanel/no-typo-column-keyword": "warn",
    },
  },
];

Rules

| Rule | Type | Fixable | | --- | --- | --- | | prefer-shorthand-filter | suggestion | yes | | audit-row-action-needs-confirm | problem | no | | no-server-import-in-client | problem | no | | require-unique-resource-names | problem | no | | no-typo-column-keyword | problem | yes |

prefer-shorthand-filter

When every entry of options: inside a filters: [...] array has label === value, the array can be written as a string array. The runtime normalizes both shapes to the same thing.

// bad
filters: [
  {
    key: "status",
    type: "select",
    options: [
      { label: "active", value: "active" },
      { label: "archived", value: "archived" },
    ],
  },
];

// good (auto-fixable)
filters: [
  { key: "status", type: "select", options: ["active", "archived"] },
];

audit-row-action-needs-confirm

An entry in actions: [...] or bulkActions: [...] with variant: "destructive" and no sibling confirm: property is reported. You have to provide the message yourself, so this rule is not auto-fixable.

// bad
actions: [
  { key: "delete", label: "Delete", variant: "destructive", run },
];

// good
actions: [
  {
    key: "delete",
    label: "Delete",
    variant: "destructive",
    confirm: "Are you sure?",
    run,
  },
];

no-server-import-in-client

In a file that starts with "use client", importing a server-only module ships server code to the browser. The rule flags:

  • server-only and */server-only
  • any path containing a /server/ (or terminal /server) segment
  • @/db, @/db/... (and the ~/db, src/db, ./db variants)

require-unique-resource-names

Within a single defineAdmin({ resources: [...] }) call, every resource() entry must resolve to a unique name. This rule looks at opts.name when it is a string literal; names inferred from the ref at runtime are handled by the runtime validator.

no-typo-column-keyword

Heuristic check for common camelCase typos in columns: [...] (string form or object form with key/name). v1 only catches a short list of known typos: userid, createdat, updatedat, isactive. Full schema-aware validation is tracked separately.

License

MIT