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

@strastdas/oxc-config

v0.2.0

Published

Shared Oxlint compatibility presets for Ultracite projects.

Readme

@strastdas/oxc-config

Shared Oxlint compatibility presets for repositories using Ultracite.

See QUALITY.md for the organization-wide adoption, formatting, exception, and CI policy.

Requirements

  • Node.js ^20.19.0 || >=22.12.0
  • oxlint ^1.74.0
  • oxfmt ^0.59.0
  • ultracite ^7.9.4

Quick setup

Run this in a consumer repository to install the package and its peer dependencies, auto-detect the profile (Next.js present → next-react, otherwise base), write oxlint.config.ts/.mjs and oxfmt.config.ts/.mjs, add the required check scripts, and drop the Claude Code skill into .claude/skills/oxc-config/SKILL.md:

npx @strastdas/oxc-config

Override auto-detection with npx @strastdas/oxc-config --profile=base or --profile=next-react. The command is idempotent: it skips writing any config file or script that already exists. The scaffolded oxfmt.config.* is a starting point, not a finished config — see Formatting below for what to review afterward.

Manual setup

Install the package alongside its peer dependencies:

pnpm add -D @strastdas/oxc-config oxfmt oxlint ultracite

Next.js + React

Create oxlint.config.ts:

import { defineConfig } from "oxlint"
import nextReactConfig from "@strastdas/oxc-config/next-react"

export default defineConfig({
  extends: [nextReactConfig],
  ignorePatterns: nextReactConfig.ignorePatterns,
})

The profile combines Ultracite's core, Next.js, and React presets. It disables only these compatibility rules from the original migration pilot:

  • eslint/func-style
  • eslint/no-inline-comments
  • eslint/require-unicode-regexp
  • eslint/sort-keys
  • unicorn/filename-case

Base profile

For a non-framework project, import @strastdas/oxc-config/base instead. Framework-specific presets can then be added in the consumer config.

Formatting

Oxfmt is the canonical formatter. Each repo owns its oxfmt.config.* (formatter compatibility is inherently local), but start from Ultracite's shared defaults rather than from scratch. Quick setup scaffolds this automatically; the manual equivalent for a Next.js/React repo is:

import { defineConfig } from "oxfmt"
import ultraciteConfig from "ultracite/oxfmt"

export default defineConfig({
  ...ultraciteConfig,
  ignorePatterns: [
    ...(ultraciteConfig.ignorePatterns ?? []),
    // repo-specific: generated code, native platform folders, vendor dirs
  ],
  sortTailwindcss: {
    functions: ["clsx", "cn", "cva", "tw"],
  },
})

Drop sortTailwindcss for the base profile (non-Tailwind projects). Only add ignorePatterns entries beyond Ultracite's defaults, and only for paths this repo actually has (see QUALITY.md).

Verification

Run npm test before publishing. The pack smoke test creates a tarball, installs it into a clean temporary consumer with the peer dependencies, and imports both public profiles.