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

webpack-oxc-parsing-adapter

v0.1.0

Published

Webpack adapter that swaps the default acorn-based parsing pipeline for oxc-parser.

Downloads

121

Readme

webpack-oxc-parsing-adapter

A drop-in adapter that replaces webpack's default acorn parser with oxc-parser — a high-performance Rust-based JavaScript/TypeScript parser.

How it works

Webpack exposes a module.parser.javascript.parse hook that lets you supply a custom parse function. This adapter wraps oxc-parser and translates its output into the ESTree-compatible shape that webpack expects, including:

  • Lazy loc resolution via binary search over line-start offsets (avoids computing locations for every node up front)
  • Semicolon position tracking for ASI (automatic semicolon insertion) detection
  • Transparent proxying of nested AST nodes so that location data is only computed on demand

Requirements

  • Node.js >=18.0.0
  • webpack ^5.0.0

Installation

npm install webpack-oxc-parsing-adapter

webpack is a peer dependency. If it is not already installed:

npm install --save-dev webpack

Usage

In your webpack.config.js, import the adapter and pass it to module.parser.javascript.parse:

const oxcParse = require("webpack-oxc-parsing-adapter");

/** @type {import("webpack").Configuration} */
module.exports = {
  module: {
    parser: {
      javascript: {
        parse: oxcParse,
      },
    },
  },
};

That's all — webpack will now use oxc-parser for every JavaScript module in the build.

Example

A minimal working project lives in the example/ directory.

example/
  src/
    index.js   # entry point
    math.js
    greet.js
  webpack.config.js
  package.json

To run it:

cd example
npm install
npm run build

The compiled output is written to example/dist/.

API

The adapter exports a single function with the signature expected by webpack:

function oxcParse(sourceCode: string, options: ParseOptions): ParseResult

| Parameter | Type | Description | |--------------|----------------|------------------------------------------| | sourceCode | string | The JavaScript/TypeScript source to parse | | options | ParseOptions | Webpack parse options (sourceType, etc.) |

Returns a ParseResult object with ast, comments, and semicolons.

License

MIT @ Even Stensberg