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

@statewalker/webrun-modules-build

v0.1.2

Published

Batch module builder: drives the shared @statewalker/webrun-modules preprocess core through @statewalker/webrun-builder's BuildEngine with an ext-map URL policy, emitting a static .js/.css tree to a cache FilesApi.

Downloads

270

Readme

@statewalker/webrun-modules-build

Batch module builder. Drives the shared @statewalker/webrun-modules preprocess core through @statewalker/webrun-builder's BuildEngine with an ext-map URL policy (every emitted module is a static .js), emitting a static .js tree to a cache FilesApi.

Pipeline

scanner → sources → [Classify] → module/css/json → [Preprocess] → served → [Serve]
                                                        └ [Prune] on sources-removed
  • Classify routes each scanned source to a module / css / json signal.
  • Preprocess walks the entry's transitive closure via walkFrom, emitting the entry + project deps as .js, plus the ~deps proxy bodies and resolved npm endpoints as side-effects into cache, then wraps JSON/CSS ids into their static .js forms.
  • Prune removes a deleted source's emitted artifact + sidecars.
  • Serve collects the emitted entry pointers.

Incremental gating

newProjectBuild installs an opt-in ctx.skipTransform hook consulted by walkFrom for every closure node (entry, interior, and shared). It reuses the emitted artifact when the source is byte-identical to a per-id content-hash sidecar and the artifact still exists — so editing a root re-transforms only the root, and a diamond transforms its shared node once, not once per path. project and cache must be distinct FilesApi instances (asserted).

CSS emission

  • CSS reached from JS emits a .js injector. An import "./styles.css" from JS becomes one cssModuleWrapper .js that injects a <style>.
  • F2 — @import-chained .css is emitted as a real file. An @import "./other.css" keeps its .css specifier; the chained stylesheet is written as a live .css at its urlPath (alongside its .js form) so the injected @import resolves.
  • F3 — url() asset references are copied. url("./logo.png") targets a non-code asset id, copied verbatim to its (unchanged) ext-map path.