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

@intentic/constants

v1.317.0

Published

Shared constants for the intentic packages, ports, paths, and image references the daemon, CLIs and desktop app all agree on

Readme

constants

The values several packages must agree on (ports, workspace paths, origins, install-script URLs, the sign-in client id, the hosted price ladder), defined once so no copy drifts.

flowchart LR
    c(["constants"])
    c -->|"index: browser-safe values"| web["Web app · public site"]
    c -->|"index"| daemon["Daemon · platform api · CLIs"]
    c -->|"./node: repoRoot"| scripts["Scripts, configs,<br/>dev servers"]
    c -->|"plain .mjs tables"| gates["_tools/checks · verify scripts<br/>daemon's own checks"]
  • The index has no Node imports, so the web app and the public site bundle the same values the daemon reads. It also carries the provider logos, the arrival profiles (profile.ts) and the hosted machine ladder (hosted-tiers.ts), whose prices the site, the Billing page and the platform config all state.
  • ./node holds repoRoot and packageRoot, which find the monorepo by walking up to pnpm-workspace.yaml instead of counting ../... The paths check refuses counted roots.
  • The .mjs modules (control-bytes, contract-shrink, assertion-measure, mirror-roots, test-suites, vocabulary, ci-infra-steps, memory-room, allow, heavy-rules) are plain JavaScript with .d.mts types, so the checks and the verify scripts import them by path before any install or build, and the daemon applies the same rule from the same file.
  • heavy-rules.cjs is the one heavy-command table (which programs queue, their pools, max-holds and deadlines, and the owner's overrides merged on top); heavy-hook.cjs (a node --require preload) and heavy-exec.cjs (behind the sandbox's wrappers for native programs) judge a program by what it is as it starts. CommonJS, so the hook loads on any Node an agent's project pins.
  • memory-room is the one formula for whether the sandbox has room (limit, used, free, stall, and what each workload class costs). The daemon's resource budget judges by it, and it is also the memory-room command queue-run asks: it asks the daemon's room socket, and applies the formula itself where no daemon answers.
  • ./allow reads the two exception forms every check and guard suite honours: the site pragma // allow(<check>): <reason> and the commit trailer Allow: <check> — <reason>.
  • WORKSPACE_ROOT and HISTORY_ROOT are defaults only: a running daemon reads its real roots from config.

Key files

  • src/index.ts — ports, workspace paths, origins, install scripts and the Google client id.
  • src/node.mjs — repoRoot and packageRoot, the found-not-counted roots.
  • src/hosted-tiers.ts — every hosted machine rung, what it costs to run and what it sells for.
  • src/profile.ts — the named arrival profiles the site, the app and the platform share.
  • src/vocabulary.mjs — the words this repository retired and what each became.

Commands

pnpm --filter @intentic/constants test