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

@gesslar/muddy

v1.5.0

Published

The red-headed stepchild of muddler.

Readme

muddy

HEY!

HEY!

Do you love muddler?? ME TOO!!! If you don't, then you it only stands to reason that you are entirely ignorant of the amazing work of @demonnic. And that is inexcusable. Because he is a god and you need to worship at the altar that is his amazing work.

That said, I wish it weren't written in Java, cos I can't help. :'(

But I know a few bars of JavaScript.

I have tried to make muddy work as closely to muddler as I could. Maybe it worked, maybe I failed miserably. idfk, it Works on My Computer™.

My version is a clean-room implementation and I haven't even peeked at demonnic's, because, frankly, as implicated above, I am woefully inadequate for the Java. Which, honestly? I'm fine with.

So, if you want to use muddy, the syntax is the same. The structure it expects is the same. The output is... errr, probably... the same... ish?

I'm not gonna re-teach you how to use an identical cli-based thing, when, to repeat, the amazing god that is demonnic has already strived... strove... striven? to do it already and it's great.

The only difference between invoking muddy over muddler is the cli.

Immediate Invocation

# npm
npx @gesslar/muddy --help

# npm
npx @gesslar/muddy --help

Install as a dependency, if you want, you don't have to

# npm
npm add -d @gesslar/muddy

# npm
npm i -d @gesslar/muddy

Post Hocktuah

Also, shout out to @Edru2 for DeMuddler which is just sex on a stick.

Which is exactly how everybody likes their sex, yes? Yes. Okay.

Features unique to muddy

Add modules

muddy can scaffold new modules directly from the command line using --add. This creates the type directory (if needed), adds an entry to the {type}.json with all available fields from the schema pre-filled, and creates an empty .lua file — ready for you to fill in.

# Add a named script
muddy . --add script --name "My Script"

# Add an alias with auto-generated temp name (new_alias_1, new_alias_2, ...)
muddy . --add alias

# Short form
muddy . -a trigger --name "Health Warning"

Valid types: alias, key, script, timer, trigger.

Ignore patterns

muddy supports an ignore field in your mfile that lets you exclude files from both module collection and resource injection. This is not available in muddler.

Add an ignore array to your mfile with glob patterns:

{
  "package": "MyPackage",
  "version": "1.0.0",
  "ignore": ["**/drafts/**", "**/wip/**", "**/experimental_*"]
}

Patterns are matched against relative paths within src/. They apply to:

  • Module collection — any scripts.json, aliases.json, etc. matching an ignore pattern will be skipped entirely, along with their associated Lua files.
  • Resource injection — any files under src/resources/ matching an ignore pattern will not be copied into the .mpackage.

Standard glob syntax is supported (e.g. *, **, ?). If ignore is omitted or empty, all files are included as usual.

License

@gesslar/muddy is released into the public domain under the 0BSD.

This package includes or depends on third-party components under their own licenses:

| Dependency | License | | --- | --- | | @gesslar/actioneer | 0BSD | | @gesslar/colours | 0BSD | | @gesslar/toolkit | 0BSD | | adm-zip | MIT | | commander | MIT | | xmlbuilder2 | MIT |

Postmate

did you know there's a javascript.com?? I just found that out. holy shit.