lspmesh

---

Nordcom Commerce is a production-grade, multi-tenant storefront platform that serves many tenants from a single deployment. It pairs Next.js 16 with Shopify as the commerce backend and a Convex-backed data + content layer, and ships an operator dashboard, a marketing site, and a small set of reusable packages — all in one TypeScript monorepo.

Highlights

• Multi-tenant out of the box. A single Next.js deployment serves arbitrarily many shops; tenants are resolved by hostname in middleware and routed under a /[domain]/[locale]/… segment, so adding a new shop is a database row, not a deploy.
• Headless commerce. Shopify Storefront API for catalog/cart/checkout, Shopify Admin API for back-office operations, all behind a uniform fetch layer.
• Composable content. Descriptor-defined CMS blocks and structured documents drive marketing pages, navigation, and component-level CMS overrides — authored in the admin app's editor, stored in Convex, and rendered by the storefront via @nordcom/commerce-cms.
• i18n that respects shops. Locales live on the shop record; fallbacks degrade from request → shop default → platform default with recursion guards.
• Edge-friendly caching. Per-tenant, per-entity cache tags with surgical Shopify webhook revalidation and CMS-driven revalidateTag hooks.
• Type-safe end to end. Strict TypeScript, noUncheckedIndexedAccess, and a typed error hierarchy used uniformly across packages.
• One toolchain. Turborepo + pnpm workspaces, Biome for lint/format, Vitest for tests — no ESLint, no Prettier, no surprises.

Quick start

Prerequisites: Node.js (see .nvmrc) and pnpm. The data layer is Convex — local development runs against a local backend (no database server, no cloud account), booted and seeded automatically.

# 1. Install dependencies.
pnpm install

# 2. Configure environment variables. See .env.example for the full list. The Convex
#    vars default to the local backend on :3210, so the defaults work out of the box.
cp .env.example .env
# Required at minimum: AUTH_SECRET, SERVICE_DOMAIN.

# 3. Build the workspace packages (apps depend on each package's dist/).
pnpm build:packages

# 4. Start everything. `pnpm dev` first runs `pnpm convex:local`, which boots a
#    persistent local Convex backend on :3210, pushes the functions, and applies the
#    advanced canonical seed — then launches the apps against it.
pnpm dev

Local Convex backend. pnpm dev is local-first: it depends on pnpm convex:local (a persistent anonymous backend in .convex-local/, seeded with an advanced demo shop nordcom-demo-shop.com plus a minimal minimal-demo.com). Manage it with pnpm convex:local (boot + seed, idempotent), pnpm convex:local:reset (wipe + reseed), and pnpm convex:local:stop. To use a cloud deployment instead, point CONVEX_URL / NEXT_PUBLIC_CONVEX_URL / CONVEX_SERVER_SECRET at it. CI runs its integration and e2e suites against the same seeded local backend — no production Convex in CI.

You should now have:

App	URL
Storefront	https://storefront.localhost
Admin	https://admin.localhost
Landing	https://landing.localhost

One-time setup: install portless globally (npm install -g portless), then run portless trust (adds the local CA to the system trust store — requires a sudo prompt). pnpm dev will start the proxy automatically.