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

@loj-lang/cli

v0.6.4

Published

Temporary Loj Community CLI shell that forwards compilation and scaffold commands to Loj Cloud

Readme

@loj-lang/cli temporary shell

This package is staged from packages/loj-shell-cli and published as @loj-lang/cli during the temporary Community remote-compile period.

The installed loj command forwards compile and scaffold commands to a remote Loj gateway, then downloads generated artifacts back to the local workspace. Commands that start local services or run local package managers remain local work and are intentionally not forwarded.

Remote artifact logs are replayed to stderr with a [loj remote] prefix after the artifact is downloaded. Command stdout remains reserved for the forwarded CLI output.

loj init and loj project scaffold write starter projects back to the requested local directory. When --bootstrap is passed, the shell first materializes the remote scaffold and then runs the package installation and bootstrap script locally. loj host init --install follows the same rule for the local host/ scaffold.

Project diagnostics and standalone artifact-family commands are also routed through the gateway: loj doctor, loj rules validate|build, loj flow validate|build, and loj formula validate|build. When those build commands use --out-dir, the result is written back under the synchronized local workspace.

The package is distributed under the Loj Community EULA. Run loj --help for current command support and EULA acceptance instructions.

Publish checklist

This workspace package is named @loj-lang/shell-cli only to keep the source tree separate from the historical compiler CLI. The publish staging script rewrites the npm package name to @loj-lang/cli and adds both loj and loj-shell binaries:

npm run publish:dry-run --workspace=@loj-lang/shell-cli

For a formal 0.6.4 publish, use one of these authenticated paths:

# Interactive account with npm 2FA:
npm run build --workspace=@loj-lang/shell-cli
npm run stage:npm --workspace=@loj-lang/shell-cli
npm publish packages/loj-shell-cli/dist-npm/@loj-lang-cli-shell --access public --otp <otp>

# CI or unattended release with a granular automation token that can bypass publish 2FA:
NODE_AUTH_TOKEN=<automation-token> npm publish packages/loj-shell-cli/dist-npm/@loj-lang-cli-shell --access public

Do not retry unattended publishing with an interactive npm session that requires one-time passwords; npm will reject the publish after staging succeeds. Bump LOJ_SHELL_CLI_PUBLISH_VERSION for each retry because npm versions are immutable once accepted.

If you still need to reproduce the earlier preview channel, keep using npm run publish:shell-preview --workspace=@loj-lang/shell-cli with an explicit preview version such as LOJ_SHELL_CLI_PUBLISH_VERSION=0.6.4-shell.1.