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

@trailpack/react-codeconventions

v0.1.1

Published

Shared minimal oxlint + oxfmt config for Trailpack React projects.

Readme

@trailpack/react-codeconventions

Shared, minimal oxlint + oxfmt configuration for Trailpack React projects. Install once, extend per project.

The base config is intentionally the absolute minimum — the react plugin with the correctness category as errors, plus a small formatting style. Each consuming project layers its own plugins and rules on top.

Install

oxlint (and optionally oxfmt) are peer dependencies — the consuming project owns their versions, so you can bump them or add plugins independently.

pnpm add -D @trailpack/react-codeconventions oxlint oxfmt

Linting (oxlint)

Create .oxlintrc.json in the consuming project. extends takes a file path into node_modules, then add your own plugins / rules on top — later values win, so you can extend or override anything in the base:

{
  "extends": ["./node_modules/@trailpack/react-codeconventions/oxlintrc.json"],
  "plugins": ["react", "typescript", "jsx-a11y"],
  "rules": {
    "no-console": "warn"
  }
}

Run it:

{
  "scripts": {
    "lint": "oxlint"
  }
}

Prefer a TypeScript config? oxlint also supports importing this package directly from oxlint.config.ts:

import { defineConfig } from 'oxlint';
import base from '@trailpack/react-codeconventions/oxlint' with { type: 'json' };

export default defineConfig({ extends: [base] });

Formatting (oxfmt)

oxfmt has no extends, so it never picks up this package on its own. You always need an oxfmt.config.mts in the project — that file is what pulls in the shared config. oxfmt auto-discovers it (CLI and editor format-on-save), so no -c flag is needed.

Create oxfmt.config.mts — this is the minimum required to use the config:

// oxfmt.config.mts
import base from '@trailpack/react-codeconventions/oxfmt' with { type: 'json' };

export default base;

Add the scripts:

{
  "scripts": {
    "format": "oxfmt .",
    "format:check": "oxfmt --check ."
  }
}

That's it. If you additionally want to override something in this project, spread the base in the same file instead of exporting it directly:

import base from '@trailpack/react-codeconventions/oxfmt' with { type: 'json' };

export default { ...base, printWidth: 120 };