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

@selorax/pages-cli

v0.1.17

Published

SeloraX Pages CLI — pull/dev/deploy/build/create for file-based storefront projects.

Readme

@selorax/pages-cli

The CLI for the SeloraX Pages platform — pull, edit, preview, deploy, and self-host file-based storefront projects. Command: selorax-pages.

npm i -g @selorax/pages-cli
# or: npx @selorax/pages-cli <command>

0.1.15 · pre-1.0.

Not the extensions CLI. @selorax/cli (command selorax) is the separate SeloraX extensions developer CLI. This package — @selorax/pages-cli (command selorax-pages) — is for the AI-native page/storefront platform.

What it is

A SeloraX Pages storefront is a folder of files (Next-app-router-shaped). This CLI is the developer's entry point to that workflow: a thin HTTP client over the storefront API (/storefront/v1) plus a local renderer and a self-host builder. It never touches storage directly — it talks to the API with a per-tenant key.

The project tree

routes/                 pages by path; _layout.{html,tsx} = directory-scoped layout
  index.html            e.g. → /
  products/[slug].tsx   dynamic route
components/             shared TSX imported by pages
partials/               Liquid {% include %} fragments
selorax.json            { apiUrl, storeId, domain }

Commands

selorax-pages pull <dir>   --api <url> --store <id> [--domain <d>] [--force]   # download the project
selorax-pages dev  <dir>   [--port 4321] [--watch]                            # local render, no round-trip
selorax-pages deploy <dir> [--prune] [--dry-run] [--force]                    # push edits (skips unchanged)
selorax-pages build <dir>  [--out <dir>] [--vendor]                           # emit a self-hostable Next app
selorax-pages create   <dir> --api <url> --store <id> [--domain <d>]            # scaffold a starter project
selorax-pages validate <dir> [--json]                                           # lint locally (offline) — routes, includes, imports, tags
selorax-pages status   <dir> [--json]                                           # show local changes vs. the live store
  • pull → writes the project tree + a loose tsconfig.json/sx-env.d.ts (so editors stay quiet).
  • dev → boots the renderer locally against the pulled files, compiling on the fly. --watch adds SSE live-reload (auto-refresh on save).
  • deploy → walks the tree and POSTs each page/layout (attaching components + partials); additive, a new version per file. Diffs against the live store first (GET /project) and skips unchanged routes/assets — a shared component/partial change re-pushes all pages (they bundle it). Flags: --prune deletes remote pages/assets no longer present locally (draft-only editor pages are never touched); --dry-run prints the plan and writes nothing; --force redeploys everything.
  • build → precompiles to a self-hostable thin Next app. Deps default to the published @selorax/*@^0.1.0; --vendor instead bundles tarballs (offline/pre-publish).
  • create → scaffolds an HTML+TSX starter (home, product, cart, checkout, collection) + an AGENTS.md authoring guide.
  • validate → offline structural + cross-reference lint: route validity, {% include %} / TSX import resolution, balanced {{#each}}/{{#if}}, section-type references, JSON parse, @type slug shape. Exit 1 on errors; --json for tooling/agents. deploy runs this first (skip with --force).
  • status → read-only: which routes/assets are changed, new, unchanged, or remote-only vs. the live store. Reuses the deploy planner, writes nothing. --json for tooling.

Auth

A per-tenant secret key via the SELORAX_TOKEN env var (or a project .env):

SELORAX_TOKEN=sk_live_… selorax-pages pull mystore --api https://your-host/api/storefront/v1 --store 22

Global flags

--help (or -h) prints usage; <command> --help prints command usage. --version (or -v) prints the CLI version. --json makes validate, status, and deploy emit machine-readable output (for CI and AI agents).

The loop

pull  →  edit / selorax-pages dev  →  selorax-pages deploy   (host on SeloraX)
                                   └─  selorax-pages build    (self-host: bun install && bun run build && bun run start)

Part of SeloraX Pages

@selorax/data · @selorax/runtime · @selorax/platform · @selorax/compiler · @selorax/pages-cli