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

@usine/expression

v0.2.0

Published

CEL expression seam for usine: check and evaluate the selection expressions loop files use.

Readme

@usine/expression

Typed CEL checking and evaluation for usine. Callers describe object types and root variables with Environment, then use ExpressionEngine to check boolean trigger expressions, check scalar prompt expressions, or evaluate either form over plain JSON.

Unknown variables and object paths fail during checking, including paths inside CEL macros such as exists. Failures are typed values: ExpressionCheckError from parsing, type checking, or result-type checking, ExpressionEvaluationError from evaluation, and the ExpressionError union covering both. JSON integers declared as CEL int or uint are converted to bigint before evaluation so GraphQL payloads keep CEL integer semantics.

relatedStringLiterals(source, memberPath) reports string literals from the smallest expression subtrees that use a member path. Config validation uses it to diagnose undeclared GitHub labels without coupling @usine/config to the CEL adapter's AST.

MarcbachmannCelLayer uses @marcbachmann/[email protected]. The exported ExpressionEngine contract contains CEL type names and usine-owned descriptors rather than library objects; an @bufbuild/cel adapter can provide the same service tag without changing callers.

All APIs remain 0.x and can change between minor releases.

Import ExpressionEngine, Source, Environment, the environment descriptors, Scalar, and the typed expression errors from @usine/expression/expression-engine. This entry point replaces @usine/expression/model; existing imports from that subpath must use /expression-engine. Import the CEL adapter layer separately from @usine/expression/marcbachmann-cel.