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

@draft0/oxlint

v0.1.0

Published

Opinionated Oxlint presets to help you ship faster.

Readme

@draft0/oxlint

Skip setup, start shipping.

⚠️ This package is in beta preview and its API is subject to change.

@draft0/oxlint is part of Draft0, an opinionated, zero-configuration toolkit for modern TypeScript projects.

This package provides an Oxlint preset so you can get strict, framework-aware linting defaults out of the box and focus on shipping features.

Install

npm install -D @draft0/oxlint oxlint

Usage

// oxlint.config.ts
import { defineConfig } from "@draft0/oxlint";

export default defineConfig();

Options

presets

defineConfig starts with Draft0's opinionated core preset. Add the presets that match your stack with draft0.presets, and Draft0 will pull in the pieces those presets need.

import { defineConfig } from "@draft0/oxlint";

export default defineConfig({
  draft0: {
    presets: ["nextjs", "vitest"],
  },
});

For example, nextjs includes react, and react includes jsx, so draft0.presets: ["nextjs"] produces a config built from core, jsx, react, and nextjs in that order. Repeated presets are ignored, and your local config is applied last so explicit overrides still win.

Available presets: core, jsx, analog, angular, astro, ember, lit, nestjs, nextjs, nuxt, preact, qwik, react, reactNative, reactRouter, remix, solid, svelte, svelteKit, tanstackStart, vue, jest, playwright, vitest

nested

Oxlint supports per-directory configs: it lints each file using the nearest oxlint.config.ts (or .oxlintrc.json) walking up from that file. Configs are not merged automatically across directories - see Nested configuration files.

A few top-level Oxlint settings are root-only. In particular, options.typeAware and options.typeCheck make Oxlint error if they appear in a nested config. Since @draft0/oxlint's core preset turns those on, a per-package config built from the preset would otherwise fail to lint.

Set draft0.nested: true in any package-level config so the root-only options are stripped from the result. Leave it off (the default) for your repo's root oxlint.config.ts.

// packages/web/oxlint.config.ts
import { defineConfig } from "@draft0/oxlint";

export default defineConfig({
  draft0: {
    nested: true,
    presets: ["nextjs"],
  },
  rules: {
    "eslint/no-console": ["off"],
  },
});

esm

draft0.esm controls whether ESM-first rules are enabled. It defaults to true. Set it to false for CommonJS projects to apply CommonJS-oriented overrides.

import { defineConfig } from "@draft0/oxlint";

export default defineConfig({
  draft0: {
    esm: false,
  },
});

Merge priority

The config object you pass to defineConfig(...) is treated as your local ("self") config and is applied last. That means your explicit fields always override preset defaults.

import { defineConfig } from "@draft0/oxlint";

export default defineConfig({
  draft0: {
    presets: ["nextjs"],
  },
  rules: {
    // Overrides rule level from presets
    "eslint/no-console": ["error"],
  },
});

Documentation

Full documentation: draft0.dev.