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

@mastermunj/oxc-config

v0.0.2

Published

Shared oxlint + oxfmt configuration for TypeScript packages

Readme

@mastermunj/oxc-config

Shared Oxlint and Oxfmt configuration for TypeScript packages.

What this package provides

  • Shareable oxlint base config
  • Shareable oxfmt base config
  • A simple starting point that teams can customize per package

Install

npm install --save-dev @mastermunj/oxc-config oxlint oxfmt oxlint-tsgolint@latest

Usage

1) Oxlint config

Create .oxlintrc.json in your project root:

{
  "extends": ["./node_modules/@mastermunj/oxc-config/.oxlintrc.json"]
}

2) Customize lint rules on top

Yes, you can both override existing rules and add new rules.

Example:

{
  "extends": ["./node_modules/@mastermunj/oxc-config/.oxlintrc.json"],
  "rules": {
    "typescript/no-explicit-any": "warn",
    "no-console": "error"
  },
  "overrides": [
    {
      "files": ["scripts/**/*.ts"],
      "rules": {
        "eslint/no-console": "off"
      }
    }
  ]
}

3) Oxfmt config

Use the shared formatter config via --config:

oxfmt --check --config ./node_modules/@mastermunj/oxc-config/.oxfmtrc.json .
oxfmt --write --config ./node_modules/@mastermunj/oxc-config/.oxfmtrc.json .

4) Scripts

{
  "scripts": {
    "lint": "oxlint --type-aware .",
    "lint:fix": "npm run lint -- --fix",
    "format": "oxfmt --check --config ./node_modules/@mastermunj/oxc-config/.oxfmtrc.json .",
    "format:fix": "oxfmt --write --config ./node_modules/@mastermunj/oxc-config/.oxfmtrc.json ."
  }
}

5) Customize formatter settings

oxfmt does not currently support deep config inheritance like lint extends in the same way.

Recommended approach:

  • Start from the shared config file
  • Copy into your package as .oxfmtrc.json
  • Adjust only settings you want to change

Package Exports

  • @mastermunj/oxc-config/oxlint
  • @mastermunj/oxc-config/oxfmt

License

MIT