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

@itslil/unified

v11.0.7

Published

unified processor reimplemented in LilScript

Readme

@itslil/unified

Official [email protected] algorithms rewritten in LilScript. Official test suite 195/195. Not affiliated with upstream.

Site: yeargun.github.io/unifiedlil/ · Pipeline lab: yeargun.github.io/unifiedlil/pipeline.html

npm install @itslil/unified

Two compiles ship from the same .lil source:

| Lane | Config | Meaning | | --- | --- | --- | | library (npm) | lilscript.toml · --target js-module | reusable ESM. Export names and extern class keys stay. | | closed | lilscript.closed.toml · --target js-module | closed LilScript world. Public and extern property names are preserved; eligible internal owned properties may be mangled. ESM export names stay so the lane is testable. |

You publish the library lane. The closed artifact is dist/unified.closed.js.

vfile imports #minpath, #minproc and #minurl per export condition: node:path, node:process and node:url's fileURLToPath under node, its own small shims everywhere else. This package resolves the same way. Under node (Node, Deno, Bun) @itslil/unified and @itslil/unified/vfile give dist/unified.node.js and dist/vfile.node.js, which import those three Node modules as vfile does; every other runtime (browsers, workers, edge runtimes, React Native) gets dist/unified.esm.js and dist/vfile.esm.js, which carry the shims. test/environments.test.mjs bundles upstream vfile and this package with each runtime's conditions and compares the working directory, every path getter and setter, file URLs and the errors they throw.

The compiler writes the ESM, CommonJS and UMD files directly. Native Node imports are declared in the staged source graph; browser and worker entries use the portable shims. Format wrappers and module linking are part of compiler delivery, with no post-compilation JavaScript minifier.

ESM, CommonJS, UMD, and closed artifacts directly contain the pure LilScript VFile runtime. VFile-compatible inputs retain their identity in every format. The same implementation is available as @itslil/unified/vfile in ESM and CommonJS.

The current public comparison is generated from independently targeted raw, gzip and Brotli artifacts. See COMPARISON.md and package files and validation.

src/entry.lil imports src/vfile.lil directly, so processor, trough, VFile, parser-facing values, and stringifier-facing values form one LilScript graph before code generation. npm run check:sources verifies the pinned SHA-256 mapping shared with remark. npm run measure:graph compares that unmodified output with the complete official browser graph compressed by Terser 5.51.2.

The LilScript compiler lives next door at ../lilscript.

Comparison with the original

See COMPARISON.md for current size and build-time comparisons against minified upstream.

Download the checked repository package · Package files, hashes and validation. npm publication is independent.