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

@rcrsr/rill-cli

v0.8.6

Published

CLI tools for the rill scripting language

Readme

@rcrsr/rill-cli

Command-line tools for running and validating rill scripts.

Experimental. Breaking changes will occur before stabilization.

Install

npm install -g @rcrsr/rill-cli

Tools

rill-exec

Execute a rill script file.

rill-exec script.rill [args...]
rill-exec -                        # read from stdin

Positional arguments pass to the script as $ARGS:

rill-exec greet.rill alice bob
# Inside script: $ARGS == ["alice", "bob"]

Read from stdin with -:

echo '"Hello" -> log' | rill-exec -

Exit codes:

| Return Value | Exit Code | |-------------|-----------| | true or non-empty string | 0 | | false or empty string | 1 | | [0, "message"] | 0 (prints message) | | [1, "message"] | 1 (prints message) |

rill-eval

Evaluate a single rill expression. No file context or module loading.

rill-eval '"hello".len'            # 5
rill-eval '5 + 3'                  # 8
rill-eval '[1, 2, 3] -> map |x|($x * 2)'  # [2, 4, 6]

rill-check

Lint and validate rill scripts.

rill-check script.rill             # text output
rill-check --format json script.rill
rill-check --fix script.rill       # auto-fix

Options:

| Flag | Description | |------|-------------| | --fix | Apply automatic fixes | | --format text\|json | Output format (default: text) | | --verbose | Include rule category in JSON output |

Exit codes:

| Code | Meaning | |------|---------| | 0 | No issues | | 1 | Diagnostics reported | | 2 | File not found | | 3 | Parse error |

Configuration: Place .rill-check.json in the project root:

{
  "rules": {
    "NAMING_SNAKE_CASE": "on",
    "SPACING_OPERATOR": "off"
  }
}

Rule states: "on" (enabled), "off" (disabled), "warn" (downgrade to warning).

Lint rules: 30 rules across 8 categories (naming, anti-patterns, strings, types, flow, loops, collections, formatting). Run rill-check --help for the full list.

Documentation

| Document | Description | |----------|-------------| | CLI Reference | Full CLI documentation | | Language Reference | Language specification | | Conventions | Coding style and lint rationale |

License

MIT