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

motely-wasm

v26.0.2

Published

Balatro seed search + per-seed analysis via JAML. Same Motely engine as native, compiled to WebAssembly (Bootsharp).

Readme

Motely.Wasm

Two hosts. Motely.dll has no Bootsharp.

import { Search, Analyze } from "motely-wasm"

Jimmolate is MotelyIndividualSeedSearcher: JS defines (ctx) => score and binds it before boot(). ctx is the live MotelySingleSearchContext (specialization). Not a seed string.

Search.jimmolate = (ctx) =>
  ctx.getAnteFirstVoucher(1) === /* MagicTrick */ 1 ? 1 : 0;
await bootsharp.boot();
await Search.jimmolateList(["ALEEB", "PIROCKS"]);

Search.scoreList(jaml, seeds) is JAML list search. Analyze.seeds(jaml) is Jamlyzer. Both take JAML text — JamlConfig is a class and does not cross.

The seed analyzes itself. Search.settings(jaml).withAnalysis(eventRolls) makes the engine run the Jamlyzer on every find in the same pass: each Search.onScored seed is followed by its full MotelyJamlyzerSeedResult on Search.onAnalyzed, same score and tally, every ante's boss/voucher/tags/shop/packs. eventRolls: 0 is the per-ante summary only (no roll queues); 20 is what Analyze.seeds uses. Don't call Analyze.seeds for a seed the search just handed you — that is a second crossing for data the engine already had in hand.

Search.onAnalyzed = (r) => (breakdown[r.seed] = r);
await Search.settings(jaml).withAnalysis(0).withSeedList(seeds).start(token);

[RenameModule] => index. [RenameNode] erases Boot, Names, specialization Import/Export proxies.

dotnet publish Motely.Wasm/Motely.Wasm.csproj -c Release

Always -c Release. Release is NativeAOT-LLVM. -c Debug is Mono: fat, slow, not the module.