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

@momiji-rs/sasso

v0.4.0

Published

A pure-Rust SCSS to CSS compiler (a dart-sass alternative), as a tiny dependency-free WebAssembly module.

Readme

@momiji-rs/sasso

sasso — a pure-Rust SCSS → CSS compiler (a dart-sass alternative) — as a tiny, dependency-free WebAssembly module. No wasm-bindgen, no native add-ons: one small .wasm plus a hand-written loader, so it runs the same in Node and the browser.

npm install @momiji-rs/sasso
import { compile } from "@momiji-rs/sasso";

const css = compile(`
  $brand: #2a7ae2;
  .button {
    color: $brand;
    &:hover { color: darken($brand, 10%); }
  }
`);
console.log(css);

// compressed output
compile("a { color: #ffffff }", { style: "compressed" }); // a{color:#fff}

compile(scss, options?) returns the CSS string, or throws an Error with the compiler's message on a Sass error. Options: { style?: "expanded" | "compressed" }.

Two builds: size vs speed

The default import is the size-optimized build (-Oz, ~350 KB gzip). For ~2× compile throughput on a larger module (~610 KB gzip), import the speed-optimized build instead — same API, same output:

import { compile } from "@momiji-rs/sasso";        // default: smallest module
import { compile } from "@momiji-rs/sasso/speed";  // ~2x faster, larger module

Tuning the bump-arena allocator

Both builds bump-allocate a single compile from a reusable arena region, which is the bulk of the speed advantage. The region defaults to 32 MiB of wasm linear memory (grown once on the first compile, then reused). Tune or disable it with configure()before the first compile():

import { configure, compile } from "@momiji-rs/sasso/speed";

configure({ arenaMiB: 16 }); // smaller footprint (enough for typical sheets)
// configure({ arenaMiB: 0 }); // disable the arena: lowest memory, slower
compile(scss);

A stylesheet larger than the arena spills to the system allocator with no loss of correctness — just less speedup. The compile-time default is also settable when building from source: SASSO_WASM_ARENA_MB=16 bash wasm/build.sh.

For the CLI and the Rust library, see the main repository.

Licensed under MIT OR Apache-2.0.