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

@alphasquad/create-storefront

v0.2.3

Published

CLI to scaffold storefront tenants powered by @alphasquad/storefront-base

Vulnerabilities

Powered byPowered by Snyk
  • 0High
  • 0Medium
  • 0Low

Links

Git

Maintainers

aqkhanaqkhanabasitqabasitqassadakramiintellectassadakramiintellect

Keywords

Readme

@alphasquad/create-storefront

Scaffold a new AlphaSquad storefront tenant (Next.js app) powered by @alphasquad/storefront-base.

Quick Start

npx @alphasquad/create-storefront@latest my-tenant
cd my-tenant
npm install
cp .env.example .env.local
npm run dev

Fill in:

  • NEXT_PUBLIC_API_URL
  • NEXT_PUBLIC_SITE_URL

What It Generates

The scaffold is intentionally small so each tenant can build a bespoke homepage/branding while staying on the shared foundation.

  • package.json
    • Dependencies:
      • @alphasquad/storefront-base (shared foundation)
      • @alphasquad/storefront-config (typed tenant config contract)
      • next, react, react-dom (tenant-owned runtime dependencies)
  • storefront.config.ts
    • Tenant config (branding, integrations, optional head fields like title/robots)
  • app/layout.tsx
    • Uses buildBaseMetadata(storefrontConfig) and buildBaseViewport() from @alphasquad/storefront-base
  • app/page.tsx
    • Placeholder home page (replace with tenant-specific implementation)
  • next.config.ts
    • Uses createBaseNextConfig() from @alphasquad/storefront-base/runtime/next-config
    • Enables transpilePackages for the shared @alphasquad/* packages
  • tsconfig.json
  • .env.example

Keeping Tenants In Sync

Tenants should depend on @alphasquad/storefront-base (and @alphasquad/storefront-config) using semver ranges.

When you publish updates to @alphasquad/storefront-base (for example, changes to how <head> metadata is built), tenants can receive those updates via normal dependency updates (ex: Dependabot with auto-merge patch updates).