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

@modelence/runtime

v0.1.0

Published

Container entrypoint for apps deployed to Modelence Cloud

Readme

@modelence/runtime

The container entrypoint for apps deployed to Modelence Cloud. Modelence Cloud's build installs a pinned version of this package into every app image and runs modelence-runtime as the container command.

On start it reads MODELENCE_WEB (the start command and static mounts from modelence.config.json) and:

  • fetches the environment variables set in the Modelence dashboard with the container's service token and runs the start command with them. Each request times out after 10s and is retried with backoff for up to MODELENCE_ENV_FETCH_TIMEOUT seconds (default 300); a rejected token fails at once;
  • serves static mounts with single-page app fallback, when there is no start command;
  • with both, serves the mounts and proxies everything else to the app. The public port stays closed until the app opens its own; if it has not within MODELENCE_APP_START_TIMEOUT seconds (default 300), the container exits.

The app runs with HOSTNAME=0.0.0.0, so frameworks that bind to $HOSTNAME (Next.js standalone) listen on every interface; a dashboard value wins.

Zero runtime dependencies; Node.js 18 or newer.

Development

TypeScript in src/, built with tsup to dist/ (npm run build). src/bin.ts is the modelence-runtime executable and src/index.ts the importable API. npm test builds first, because the bin tests run the built dist/bin.js as a child process — the same file that ships.

Releasing

Versions are immutable and pinned by Studio, so a change here reaches tenant containers only when Studio bumps its pin. Bump version, then push a @modelence/runtime@<version> tag to publish (prepack builds dist/).