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-webpack-plugin

v1.0.2

Published

An OxLint plugin for webpack

Readme

oxlint-webpack-plugin

This plugin uses Oxlint to find and fix problems in your JavaScript code during the Webpack build process.

Getting Started

To begin, you'll need to install oxlint-webpack-plugin:

npm install oxlint-webpack-plugin --save-dev

or

yarn add -D oxlint-webpack-plugin

or

pnpm add -D oxlint-webpack-plugin

[!NOTE]

You also need to install oxlint from npm, if you haven't already:

npm install oxlint --save-dev

or

yarn add -D oxlint

or

pnpm add -D oxlint

Then add the plugin to your webpack configuration. For example:

const { OxLintWebpackPlugin } = require("oxlint-webpack-plugin");

module.exports = {
  // ...
  plugins: [new OxLintWebpackPlugin(options)]
  // ...
};

Options

Options is an object with the following possible keys:

format

  • Type:
type format = string;
  • Default: "default"

Use a specific output format.

Possible values: "default" or "stylish" (recommended).

[!NOTE]

"stylish" is shorter, more concise and better for webpack build processes.

[!NOTE]

OxLint provides several other formats, but only those mentioned above are useful in the context of webpack.

childProcessMaxFiles

  • Type:
type childProcessMaxFiles = number;
  • Default: 10

Specify the maximum number of files that should be linted individually.

This plugin spawns a new process for OxLint, which receives a list of files to be linted (oxlint file1 file2 file3 ... fileN).

When lots of files need to be linted at once, it is better to just lint the whole project. Passing tens or hundreds of arguments to the spawned process could lead to problems in some platforms.

This option specifies the threshold from which OxLint will lint the whole project instead of linting files individually.

Tweak it to your needs and the characteristics of your platform.

License

MIT