Retire the Next.js storefront

[HereLiesAz]

apps/storefront becomes the catalog only: registry/, build-catalog, build-previews and their test. Every feature it served now lives in apps/storefront-react + apps/storefront-worker (ratings, reports, moderation, per-app page, publish, privacy/terms).

• Removed: app/, components/, lib/, middleware.ts, next.config.mjs, vercel.json, scripts/{bundle,embed-docs,seed}, public/, and the Next-only tests. Next deps dropped from the lockfile.
• storefront-cmp: the wasm distribution goes to its default build directory, not ../storefront/public. The matching .gitignore block is gone.
• Docs: VitePress cleanUrls is always on, since the AZPHALT_DOCS_EMBED path is gone. README, ARCHITECTURE, OPERATIONS (cutover status), the Worker README § Domains, the marketplace and registry readmes, the deploy-docs comment, and the legal-page header comments are updated.
• Changeset: @azphalt/storefront major (private).

Effect on Vercel: builds of main will fail from here on, and Vercel keeps serving its last good deployment until the domains move to the Worker.

Overlap with #226: apps/storefront/package.json already has license: Apache-2.0 here too, so that line merges cleanly either way.

Validated with pnpm -r build, pnpm test and the docs build. All green: Worker 25, storefront 5, repository-server 54, and the rest.

🤖 Generated with Claude Code

https://claude.ai/code/session_01QwYWVPse8spRrfMMcuTJPv

---

Generated by Claude Code

Summary by Sourcery

Retire the Next.js storefront and make apps/storefront the canonical catalog source while directing production serving to the React storefront and Cloudflare Worker.

Enhancements:

• Reduce apps/storefront to the git-backed catalog and its catalog and preview build tooling, with the production storefront provided by the React UI and Cloudflare Worker.
• Remove the retired Next.js storefront, its deployment configuration, runtime features, supporting scripts, dependencies, and associated tests.
• Stop coupling the native storefront client and documentation build to the former Next.js asset and embedding paths.
• Update repository, architecture, operations, deployment, and application documentation to reflect the retired Next.js deployment and pending Worker domain cutover.

Build:

• Remove the Next.js/Vercel build and packaging configuration and related dependencies from the workspace.

Deployment:

• Document that Vercel builds are intentionally frozen and continue serving the last successful deployment until the Worker domains are attached.

Tests:

• Retain and narrow storefront validation to catalog build behavior and type checking.

Chores:

• Mark @azphalt/storefront for a major private-package release reflecting its transition to catalog-only responsibilities.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
azphalt	Error		Sep 27, 2026 5:58am UTC

[sourcery-ai]

Reviewer's Guide

Retires the Next.js storefront and removes its application, deployment, and feature code, leaving apps/storefront as the git-backed catalog builder while documenting storefront-react plus storefront-worker as the production path and the pending Cloudflare domain cutover.

Flow diagram for building and serving the git-backed catalog

flowchart LR
    Registry["registry/\nsources.json + local packages"] --> BuildCatalog["build-catalog"]
    BuildCatalog --> Verify["Verify pinned sources and integrity"]
    Verify --> BuildPreviews["build-previews"]
    BuildPreviews --> Artifacts["Committed catalog artifacts\npackages + catalog.json + previews"]
    Artifacts --> Export["storefront-react\nexport-catalog.mjs"]
    Export --> Worker["storefront-worker\nserves catalog and APIs"]

Loading

File-Level Changes

Change	Details	Files
Reduced the Next.js storefront package to a catalog build and verification package.	Deleted the Next.js app routes, UI components, server libraries, middleware, deployment configuration, scripts, static assets, and feature-specific tests. Kept catalog registry data plus build-catalog/build-previews workflows and narrowed package dependencies and TypeScript scope. Updated package documentation, license metadata, Vitest comments, and added a major changeset.	apps/storefront/app/** apps/storefront/components/** apps/storefront/lib/** apps/storefront/scripts/bundle.mjs apps/storefront/scripts/embed-docs.mjs apps/storefront/scripts/seed.ts apps/storefront/package.json apps/storefront/README.md apps/storefront/tsconfig.json apps/storefront/vitest.config.ts apps/storefront/test/** apps/storefront/next.config.mjs apps/storefront/middleware.ts apps/storefront/vercel.json .changeset/retire-nextjs.md
Removed the retired storefront's build and hosting integration points.	Stopped the native storefront WASM build from writing into the deleted Next.js public directory. Removed the associated ignore rules and Next.js dependencies from the lockfile. Documented that Vercel remains frozen on its last successful deployment until Cloudflare Worker domain cutover.	apps/storefront-cmp/build.gradle.kts .gitignore pnpm-lock.yaml apps/storefront-worker/README.md docs/OPERATIONS.md
Aligned documentation and legal assets with the Worker-based production architecture.	Made VitePress cleanUrls unconditional after removing embedded-docs support. Reclassified apps/storefront as the git-pinned catalog and storefront-react/storefront-worker as the production UI and service. Updated marketplace, registry, repository, README, architecture, deployment, and legal-page references.	docs/.vitepress/config.mjs README.md docs/ARCHITECTURE.md apps/marketplace/README.md packages/registry/readme.md apps/storefront-react/public/privacy.html apps/storefront-react/public/terms.html .github/workflows/deploy-docs.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Sorry @HereLiesAz, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 1 day and 19 hours by commenting @sourcery-ai review. Upgrade to get a review now.