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

@oxlint-config-inspector/core

v1.1.3

Published

Core config loading and inspection utilities for Oxlint Config Inspector.

Readme

@oxlint-config-inspector/core

Version Downloads License

Core config loading and inspection utilities for Oxlint Config Inspector.

This package loads an Oxlint configuration, resolves supported extends chains, loads JavaScript plugins, and returns a normalized inspection model for configured, builtin, plugin, and unknown rules.

Requirements

  • Node.js 22 or newer.
  • The oxlint binary should be available on PATH for builtin rule metadata. If it is missing, inspection still returns a result, but builtin rules are not cataloged and an error is logged.

Install

pnpm add @oxlint-config-inspector/core

Usage

import { inspectConfig } from '@oxlint-config-inspector/core'

const result = await inspectConfig({
  cwd: process.cwd(),
})

if (!result) {
  throw new Error('No Oxlint config found')
}

console.log(result.rules)

To inspect a specific config file:

import { inspectConfig } from '@oxlint-config-inspector/core'

const result = await inspectConfig({
  configFile: 'oxlint.config.ts',
  cwd: process.cwd(),
})

API

inspectConfig(options?)

Loads and inspects an Oxlint config.

Options:

  • cwd: directory to search from. Defaults to process.cwd().
  • configFile: explicit config file path, resolved from cwd.
  • cache: whether to cache discovered and loaded config files. Defaults to true.

Returns Promise<InspectConfigResult | null>. null means no config file was found.

The result includes:

  • configFilepath: absolute path to the root config file.
  • generatedAt: ISO 8601 timestamp for when the inspection result was generated.
  • configFiles: config files visited while resolving extends.
  • plugins: JavaScript plugins loaded during inspection.
  • pluginErrors: JavaScript plugin load errors.
  • rules: builtin, JavaScript plugin, and unknown rules known to the inspector.
  • stats: aggregate counts for configured, enabled, builtin, plugin, unknown, deprecated, recommended, and fixable rules.
  • unknownRules: configured rules that were not found in the builtin catalog or loaded plugins.

Config Resolution

The loader searches for:

  • vite.config.ts (Vite+)
  • .oxlintrc.json
  • .oxlintrc.jsonc
  • oxlint.config.ts

String extends entries are resolved relative to the config file that declares them. Inline object extends entries from TypeScript configs are resolved recursively. Only Oxlint's extendable fields are inherited from extended files: plugins, rules, and overrides.

JavaScript Plugins

jsPlugins entries from the root config and override blocks are loaded dynamically. Plugin load failures are reported in pluginErrors instead of throwing, so a partial inspection result can still be rendered.

Runtime

This package is ESM-only and requires Node.js 22 or newer.