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

@rustwrap/webpack

v1.0.5

Published

A webpack-compatible Node API and CLI backed by the Rolldown bundler (Rust/Oxc) for fast builds and excellent tree-shaking. Drop-in `webpack` override for pcf-scripts and webpack-based pipelines.

Readme

@rustwrap/webpack

A webpack-compatible Node API and CLI backed by the Rolldown bundler (Rust / Oxc). Drop-in replacement for webpack in pcf-scripts and webpack-based pipelines — much smaller bundles (rollup-grade tree-shaking) and far faster builds, while honouring the webpack config/API surface.

Why

Webpack bundles for Fluent-v9 PCF controls can approach the 5 MB PCF limit. Rolldown's tree-shaking removes far more dead code. @rustwrap/webpack exposes the webpack Node API + tapable plugin lifecycle that pcf-scripts and webpack plugins expect, and translates the config onto Rolldown.

Measured (representative builds)

| Build | webpack | @rustwrap/webpack | |---|---|---| | Fluent-v9 PCF control | 0.84 MB | 0.73 MB | | Multi-entry client bundle (14 entries) | 2.37 MB | 2.06 MB |

Architecture

  • lib/index.jswebpack(options, cb) factory + the full webpack.* namespace.
  • lib/compiler.js — tapable Compiler/Compilation/MultiCompiler with the standard webpack lifecycle hooks (run, make, thisCompilation, compilation, processAssets (staged), emit, afterEmit, done, …). This is what lets real third-party plugins (apply(compiler)) run.
  • lib/build.js — the make phase: runs Rolldown per entry and writes results into compilation.assets (the compiler emits them after plugins' processAssets).
  • lib/loaders.js — runs real webpack loader chains (module.rules) via loader-runner.
  • lib/css.js — native CSS pipeline (sass/less compile + style-inject or extract).
  • lib/assets.js — asset modules. lib/plugins.js — built-in plugins.
  • lib/template.js — output filename templates. lib/stats.js — Stats. lib/sourcemap.js — devtool.

Use as a webpack override

{
  "overrides": { "webpack": "npm:@rustwrap/webpack@^1" },
  "devDependencies": { "webpack": "npm:@rustwrap/webpack@^1" }
}

The CLI stubs unresolved webpack-only plugin requires (terser-webpack-plugin, webpack-bundle-analyzer, eslint-webpack-plugin, …) so existing webpack.config.js files load unchanged.

Requirements

Node.js ^20.19.0 || ^22.13.0 || >=24 (enforced via the package's engines field).

This is not an arbitrary floor — it is the exact intersection of the engine requirements of the Rust toolchain this package is built on:

| Dependency | Requires | Why | |---|---|---| | rolldown (+ native binding) | ^20.19.0 \|\| >=22.12.0 | The N-API/V8 features the Rust binary uses were backported into each LTS line at Node 20.19.0 and 22.12.0. | | eslint-scope | ^20.19.0 \|\| ^22.13.0 \|\| >=24 | Follows ESLint's policy: active LTS lines only, skipping odd non-LTS majors (21.x, 23.x). |

Taking the strictest clause on each line yields the declared range. Reading it:

  • ^20.19.0 → the Node 20 LTS line, from patch .19 up (>=20.19.0 <21). Earlier 20.x patches lack the backported native feature.
  • ^22.13.0 → the Node 22 LTS line, from patch .13 up (>=22.13.0 <23). Note this is one patch higher than Rolldown's own 22.12.0 floor, because eslint-scope requires 22.13.0.
  • >=24Node 24+ (the next even LTS line and beyond).
  • Excluded: Node ≤16 (EOL), 18.x, 21.x, 22.0–22.12, and 23.x — none satisfy every dependency.

Node 16 / 18 are not supported. Rolldown 1.x and oxlint 1.x dropped them; the native Rust binaries will not run there. The engines field makes this an immediate, named EBADENGINE warning at install (or a hard failure under engine-strict=true/CI) instead of a cryptic deep crash inside the native module.

Support matrix

✅ Supported

| Area | Notes | |---|---| | Node API | webpack(options, cb), webpack(options)→Compiler (run/watch/close), MultiCompiler (array of configs → MultiStats), function config (env,argv)=>…. | | Plugin system | Real tapable Compiler/Compilation hooks. apply(compiler) plugins run. compilation.hooks.processAssets is stage-ordered. emitAsset/updateAsset/getAsset/deleteAsset/renameAsset. webpack.sources (webpack-sources). | | entry | string / array / object / {import, filename}; [name]. | | output | path, filename, chunkFilename, clean, publicPath (asset URLs), library (string / ["NS","[name]"] / {name,type}), libraryTargetvar/window/assign→iife, umd, commonjs/commonjs2→cjs, module→es, amd. | | Filename templates | [name], [ext], [base], [path], [query], [id], [hash], [contenthash], [chunkhash] (with :N). | | mode | production/development/none → minify on/off. | | module.rules (loaders) | Real loader chains via loader-runner: test/include/exclude/resourceQuery/oneOf/enforce:pre|post/use array/options/custom loaders. JS/TS/JSX transpilation is done by Oxc (transpile-only loaders ts-loader/babel-loader/swc-loader/esbuild-loader are skipped — equivalent, faster). | | CSS | Native: .scss/.sass (consumer's sass), .less (consumer's less), .css; style-injected, or extracted when MiniCssExtractPlugin is present. CSS Modules (*.module.*) are properly scoped via postcss-modules (scoped class names + {local:scoped} export map + composes). | | Asset modules | asset/resource (emit + URL), asset/inline (data URI), asset/source, asset (auto by parser.dataUrlCondition.maxSize); generator.filename/output.assetModuleFilename. | | Node globals (browser target) | Auto-polyfills process, Buffer, and global for web builds — parity with webpack's ProvidePlugin/node-libs-browser. Using real scope analysis (acorn + eslint-scope), a process shim (nextTick/env/platform/…), the buffer package's Buffer, and global→globalThis are injected only into modules that reference them as free (unbound) identifiers. So dependencies that assume Node (e.g. telemetry SDKs pulling in readable-stream/buffer such as @aria/webjs-sdk) work in the browser instead of throwing process is not defined. No-op on target:'node' and for code that never references them. | | externals | object map / array / RegExp / sync-callback function (({request},cb) & (ctx,req,cb)) / {root} → external + output.globals. Exact-request match (webpack semantics): an entry like {react:"React"} externalizes react only, not subpaths like react/jsx-runtime (those are bundled, so e.g. the automatic JSX runtime keeps its jsx/jsxs). Externals are reachable from both import and require() — a bundled CommonJS dependency's internal require("<external>") is rewritten to the same global, so it never leaves a bare require (which would throw in the browser). | | TypeScript | Transpiled by Oxc (types stripped, JSX per tsconfig). Ambient const enum member accesses are inlined to literals (tsc parity) by reading the const enums declared in the project's .ts/.d.ts and any pulled in via tsconfig files/include or triple-slash /// <reference> — without this, accesses like XrmClientApi.Constants.X.Y would survive as runtime references to a namespace that doesn't exist at runtime. Regular (non-const) enums emit runtime objects as usual. | | resolve | alias, extensions, mainFields, mainFiles, conditionNames, modules, extensionAlias, symlinks, fallback (false→empty module), nearest tsconfig.json paths. | | devtool (source maps) | source-map, inline-source-map, hidden-source-map, nosources-*, eval-* (≈inline). Emits .map + sourceMappingURL. | | target | web (default) and node/node* (→ Rolldown platform:'node', node builtins external). | | optimization | minimize; minimizer TerserPlugin terserOptions mapped to Rolldown's minifier: compress.drop_console/drop_debugger/passes/ecma(→target)/keep_classnames/keep_fnames, mangle on/off/toplevel/keep_*, format.commentslegalComments. usedExports:false disables tree-shaking. Tree-shaking + scope-hoisting are always on via Rolldown. | | Built-in plugins | DefinePlugin (nested keys; AST-aware — replaces expressions only, never the contents of string/template literals or comments), EnvironmentPlugin, ProvidePlugin (real free-variable scope analysis via acorn + eslint-scope), BannerPlugin, IgnorePlugin, NormalModuleReplacementPlugin, SourceMapDevToolPlugin/EvalSourceMapDevToolPlugin, ProgressPlugin, optimize.LimitChunkCountPlugin (forces single chunk), LoaderOptionsPlugin, WatchIgnorePlugin, HotModuleReplacementPlugin (enables module.hot), ContextReplacementPlugin. | | Dev server / HMR | webpack serve / new webpack.DevServer(options, compiler). HTTP static serving (static), historyApiFallback, watch + rebuild, SSE live-reload, and a module.hot/import.meta.hot runtime so HMR-guarded code runs. (Hot updates apply via fast full reload — see Approximated.) | | Third-party plugins | Anything tapping compilation.hooks.processAssets/compiler.hooks.emit/done/etc. works (Copy-style, Html-style, Banner, analyzers). | | performance | hints/maxAssetSize enforced (warning/error). | | ignoreWarnings | RegExp / function filters. | | stats | Stats with hasErrors/hasWarnings/toJson/toString({colors}); quiet via stats:false|'none'|'errors-only'. | | watch | compiler.watch / watch:true with watchOptions.aggregateTimeout. | | code-splitting | dynamic import() → chunks for es/cjs output (output.chunkFilename). | | Namespace | webpack.Compiler/Compilation/MultiCompiler/sources/WebpackError/util/ModuleFilenameHelpers/version, all built-in plugins, webpack.optimize.*, webpack.container.*, webpack.ids.*. |

➖ Approximated (faithful but not byte-identical to webpack)

  • optimization.splitChunks / cacheGroups / runtimeChunk — Rolldown does its own chunking; the fine-grained cacheGroup controls are not mapped. Single-file output is preserved where required.
  • devtool: eval / eval-source-map — emit a correct inline source map (full original sources, debuggable in devtools). The literal per-module eval() wrapping is a webpack-internal rebuild mechanism and isn't reproduced on a whole-bundle engine — the debugging result is equivalent.
  • HMRmodule.hot/import.meta.hot exist and run dispose handlers, but updates apply via a fast full reload (Rolldown emits a whole bundle, not webpack hot-update chunks), so module state is not preserved across edits.
  • output.environment / target browserslist downleveling — Oxc emits modern JS; no ES5 downlevel.

❌ Not supported (Rolldown architecture / out of scope)

  • Module Federation (container.ModuleFederationPlugin is a no-op), DllPlugin.
  • experiments.asyncWebAssembly / lazyCompilation, persistent cache: {type:'filesystem'} semantics (accepted/ignored — Rolldown has its own caching).
  • Deep Compilation graph internals (moduleGraph/chunkGraph/templates) that some advanced plugins reach into.

Test

npm test runs test/run.js — a synthetic feature matrix (36 assertions) covering tree-shaking, multi-entry/MultiCompiler, Define/Environment/Banner, the loader system + CSS, custom plugins via hooks, externals, source maps, [contenthash], performance/ignoreWarnings, code-splitting, and the namespace.

Engine & dependencies

Rolldown is the bundling engine. The other deps fall into two groups:

  • Engine / compat layer (actually used by @rustwrap/webpack): rolldown, loader-runner, webpack-sources, tapable, mime-types, acorn + eslint-scope (ProvidePlugin scope analysis), postcss + postcss-modules (CSS Modules scoping).
  • webpack drop-in deps (declared so a normal npm install of the webpack override still resolves them, exactly like webpack would provide them transitively): terser-webpack-plugin (consumer configs reference it in optimization.minimizer; @rustwrap/webpack reads its options and never calls .apply()), schema-utils (required by many third-party plugins). These mirror the packages webpack itself depends on, so existing webpack.config.js files keep working after the override. The CLI additionally stubs any other unresolved webpack-only plugin require (webpack-bundle-analyzer, eslint-webpack-plugin, …) as a safety net.

@rustwrap/webpack does not implement its own bundler — the engine is Rolldown.