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

@rivuty/oxlint-config

v1.2.0

Published

Shared oxlint configurations for TypeScript projects

Downloads

30

Readme

@rivuty/oxlint-config

Shared oxlint configurations.

Installation

npm add -D @rivuty/oxlint-config oxlint
# or
pnpm add -D @rivuty/oxlint-config oxlint

Usage

Create an oxlint.config.ts in your project and import the desired config:

TypeScript projects

The typescript export enables a strict ruleset for TypeScript projects:

import { defineConfig } from 'oxlint';
import { typescript } from '@rivuty/oxlint-config';

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

Config file overrides

The config export disables rules that conflict with config files (e.g. vite.config.ts):

import { defineConfig } from 'oxlint';
import { config, typescript } from '@rivuty/oxlint-config';

export default defineConfig({
  extends: [typescript, config],
});

Vitest projects

The vitest export relaxes rules for test files (*.test.ts):

import { defineConfig } from 'oxlint';
import { typescript, vitest } from '@rivuty/oxlint-config';

export default defineConfig({
  extends: [typescript, vitest],
});

Extending

Use extends together with additional rules to customize the config:

import { defineConfig } from 'oxlint';
import { typescript } from '@rivuty/oxlint-config';

export default defineConfig({
  extends: [typescript],
  rules: {
    'no-console': 'warn',
  },
});

Exports

| Export | Description | | ------------ | ---------------------------------------------------------------------------------------------- | | typescript | Strict ruleset for TypeScript projects (all categories set to error) | | config | Overrides for config files — relaxes import/no-default-export and import/no-nodejs-modules | | vitest | Overrides for test files — relaxes rules that are impractical in tests |

License

@rivuty/oxlint-config is open-sourced under the MIT license