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

@palamedes/eslint-plugin

v1.25.0

Published

ESLint and Oxlint adapter for native Palamedes source diagnostics

Readme

@palamedes/eslint-plugin

Thin ESLint/Oxlint rule facades over Palamedes' native source analysis. The plugin does not recognize macros or implement authoring rules in JavaScript.

This package is Preview. Oxlint's JavaScript plugin API is still alpha, so pmds lint remains the stable CI and MDX interface.

Installation

Install the adapter with the host you already use:

pnpm add -D @palamedes/eslint-plugin eslint
# or
pnpm add -D @palamedes/eslint-plugin oxlint

Keep optional dependencies enabled so @palamedes/core-node can install the native package for the current platform.

ESLint flat config

import palamedes from "@palamedes/eslint-plugin";

export default [
  {
    files: ["**/*.{js,jsx,ts,tsx}"],
    plugins: { palamedes },
    rules: {
      "palamedes/no-placeholder-only-message": "warn",
      "palamedes/prefer-trans-in-jsx": "warn",
    },
  },
];

The exported configs.recommended enables no-placeholder-only-message and prefer-trans-in-jsx as warnings.

Oxlint

{
  "jsPlugins": [
    {
      "name": "palamedes",
      "specifier": "@palamedes/eslint-plugin"
    }
  ],
  "rules": {
    "palamedes/no-placeholder-only-message": "warn",
    "palamedes/prefer-trans-in-jsx": "warn"
  }
}

Rules

| Rule | Default in configs.recommended | Purpose | | ------------------------------------------- | -------------------------------- | -------------------------------------------------------------------------------------- | | palamedes/no-placeholder-only-message | warning | Reject messages made only of runtime values. | | palamedes/no-empty-component-only-message | off | Reject a single empty component placeholder; opt in when that policy fits the project. | | palamedes/prefer-trans-in-jsx | warning | Suggest Trans for safe direct JSX render positions; t remains supported. |

Each host owns rule severity and its normal inline directives:

// eslint-disable-next-line palamedes/no-placeholder-only-message
const eslintLabel = t`${status}`;

// oxlint-disable-next-line palamedes/no-placeholder-only-message
const oxlintLabel = t`${status}`;

The adapter enables every native Core diagnostic in one analysis and caches the result by filename and source fingerprint. Multiple enabled rule facades do not repeat native parsing. UTF-8 byte ranges from Rust are converted to the UTF-16 indices expected by JavaScript linters before SourceCode#getLocFromIndex maps them to editor locations.

Fatal native analysis failures are also emitted once per host parse, even when several Palamedes rules are enabled. The coordinator owns that one-shot state with the host SourceCode identity, so a later editor re-parse reports the failure again while an unchanged parse never duplicates it. ESLint-compatible hosts require diagnostics to be reported by an enabled rule, so the host ruleId is the first enabled Palamedes facade; the message explicitly identifies the diagnostic as a shared native-analysis failure, not a finding from that rule. When a native error contains Palamedes' structured at file:line:column or Location: file:line:column form, the adapter uses that source location; otherwise it safely falls back to the start of the file.

There are no fixes in this version. pmds lint suppressions are intentionally separate from ESLint/Oxlint directives and are only consumed by the CLI: this plugin does not read palamedes-lint-disable-*, and pmds lint does not read host directives, so a project running both lanes needs the directive each lane understands. The rule names differ as well — the CLI reports the native diagnostic codes (pmds/...) while this plugin exposes them under its host plugin namespace (palamedes/...).

MDX is not supported through the adapter because Oxlint JavaScript plugins do not currently support custom parsers or file formats. Use pmds lint for MDX.

The implementation rationale, benchmark, packaging risks, and reproducible LSP verification are documented in Native diagnostics through ESLint and Oxlint.

palamedes is part of the Ferramenta family — Rust-native developer tools that keep the APIs the ecosystem already knows.

Siblings: ferroni · ferriki · ferromark · ferrolex · ferrocat · ferrovia · ferralk · ferrugo.