Open Source Platform for DTC, B2B Commerce, Marketplaces & Omnichannel. REST APIs, TypeScript SDKs, and production-ready Next.js storefront. Self-host it. Own your data. No vendor lock-in. Zero platform fees.
Ruby b2b-commercee-commerceecommerceecommerce-apiecommerce-frameworkecommerce-platformheadlessheadless-commerceheadless-ecommercemarketplacemulti-tenantmulti-vendormulti-vendor-ecommerceopen-sourcespree-commerce
packages:
- "packages/*"
# catalog: the one version of every third-party package that two or more
# workspace packages install. Manifests refer to it as `catalog:`, so a bump is
# a single line here and every package moves together. Separate ranges drifted:
# Dependabot raised the apps' react-hook-form while dashboard-ui's peer range
# kept an older copy installed, and the two copies' types no longer matched.
# `pnpm publish` and scripts/sync-starter.mjs write the real range out.
#
# The catalog decides what this workspace installs and tests, not what the
# published packages promise. Peer ranges stay hand-written floors, so a host
# app or plugin on an older supported version keeps installing. @spree/
# dashboard-ui ships source and pins its runtime dependencies to the exact
# catalog version.
#
# scripts/check-dependency-ranges.mjs (CI) enforces all of this.
catalogMode: prefer
catalog:
'@base-ui/react': 1.8.0
'@biomejs/biome': ^2.4.14
'@changesets/changelog-github': ^1.0.1
'@changesets/cli': ^3.0.3
'@clack/prompts': ^1.8.0
'@dnd-kit/core': ^6.3.1
'@dnd-kit/sortable': ^10.0.0
'@dnd-kit/utilities': ^3.2.2
'@fontsource-variable/geist': ^5.3.0
'@fontsource-variable/geist-mono': ^5.3.0
'@hookform/resolvers': ^6.0.0
'@playwright/test': ^1.64.1
'@tanstack/react-hotkeys': ^0.16.0
'@tanstack/react-query': ^5.104.5
'@tanstack/react-router': ^1.170.45
'@tanstack/react-table': ^9.3.1
'@tanstack/router-plugin': ^1.168.47
'@tanstack/virtual-file-routes': ^1.162.0
'@types/node': ^26.6.5
'@types/react': ^19.2.14
'@types/react-dom': ^19.2.3
'@typescript/typescript6': ^6.0.2
'@uiw/react-json-view': ^1.12.2
'@vitejs/plugin-react': ^6.0.1
'@vitest/coverage-v8': ^5.0.5
'class-variance-authority': ^0.7.1
'clsx': ^2.1.1
'commander': ^15.0.0
'date-fns': ^4.4.0
'date-fns-tz': ^3.2.0
'execa': ^10.2.0
'flag-icons': ^7.6.0
'i18next': ^26.5.3
'lucide-react': ^1.60.0
'msw': ^3.0.3
'picocolors': ^1.1.1
'react': ^19.3.1
'react-colorful': ^5.8.1
'react-day-picker': ^10.0.2
'react-dom': ^19.3.1
'react-hook-form': ^7.90.0
'react-i18next': ^17.1.0
'recharts': 3.10.1
'shadcn': ^4.22.1
'tailwind-merge': ^3.7.0
'tailwindcss': ^4.2.4
'tsup': ^9.0.0
'tsx': ^4.21.0
'tw-animate-css': ^1.4.0
'typescript': ~7.0.2
'vite': ^8.3.4
'vitest': ^5.0.5
'yaml': ^2.9.1
'zod': ^4.6.7
# Supply-chain hardening — see https://pnpm.io/supply-chain-security
#
# minimumReleaseAge: delay installing newly-published versions of any
# dependency by 2 days (2880 minutes). pnpm 11 ships a 1-day default;
# we tighten it slightly. Catches malicious releases that get yanked
# from the registry within hours of publish without blocking ordinary
# upstream releases for a full week.
#
# blockExoticSubdeps: refuse transitive deps pulled from git URLs, raw
# tarballs, or other non-registry sources. Direct deps can still opt in
# explicitly; subdeps cannot smuggle one in. Default in pnpm 11 — pinned
# here to lock the behavior in case of future default changes.
#
# trustPolicy: fail the install if a package's trust level has dropped
# (e.g. previously signed releases now arriving without provenance).
# Defends against publisher takeover via leaked credentials.
#
# dangerouslyAllowAllBuilds: explicitly pinned to false. install scripts
# only run for packages approved via `pnpm approve-builds` — silently
# flipping this on would auto-run every dependency's postinstall.
minimumReleaseAge: 2880
blockExoticSubdeps: true
trustPolicy: no-downgrade
# Versions the lockfile has always resolved but that published without the
# provenance an earlier release had. Excluding them lets a full re-resolution
# (pnpm update) accept the same versions again; it admits nothing new.
# chokidar 4.0.3 — via tsup
# semver 6.3.1 — via @babel/core 7, which every 7.x requires
trustPolicyExclude:
- [email protected]
- [email protected]
dangerouslyAllowAllBuilds: false
# allowBuilds: per-package decision on whether install scripts run.
# dangerouslyAllowAllBuilds is off, so anything not explicitly listed
# here is silently skipped — and pnpm 11 fails the install if a needed
# build is skipped. Audit each package's install script before adding.
#
# esbuild — downloads the platform-native binary on install
# msw — copies the service-worker shim into the workspace
allowBuilds:
esbuild: true
msw: true
# overrides: force patched versions of transitive packages flagged by
# security advisories. Dependabot cannot open these PRs itself — its
# npm_and_yarn updater chokes on pnpm's `workspace:` protocol during
# security-update resolution (dependabot-core#13177) — so we pin the
# fixes here. Revisit when the upstream dependents pull the fixes in on
# their own and these become no-ops.
overrides:
# Base UI is pinned exactly, never caret-ranged: @spree/dashboard-ui ships
# source, so whatever a consumer installs is compiled into their app by
# their own Vite. A floating range means a scaffolded project builds against
# a version nobody here tested.
#
# 1.8.0 resolves @base-ui/utils 0.4.0. Do not move below it: utils 0.2.x and
# 0.3.x ship esm/store/useStore.js, which imports useSyncExternalStore BY
# NAME from the CommonJS use-sync-external-store shim. Vite converts
# CommonJS while prebundling an ordinary dependency, but an installed
# dashboard-ui is source Vite does not crawl, so that file reaches the
# browser unconverted and the dashboard dies with a SyntaxError. 0.4.0
# dropped that ESM variant. Verify any change by installing the published
# packages into the dashboard-starter template — the workspace symlink in
# this repo hides the difference.
'@base-ui/react': 1.8.0
'@base-ui/utils': 0.4.0
# react-redux 9.2.0 (transitive via recharts, whose range is 8.x || 9.x)
# published without the provenance 9.1.0 had, so trustPolicy: no-downgrade
# refuses it. 9.3.0 carries provenance again and is in range. Drop this once
# recharts resolves 9.3+ on its own.
react-redux: 9.3.0
# Still load-bearing after the 2026-10 cleanup, when every security pin a
# plain update makes redundant was dropped:
# esbuild — vite 8 still resolves 0.27.x (GHSA-g7r4-m6w7-qqqr)
# read-yaml-file — changesets' @manypkg resolves read-yaml-file 1, whose
# js-yaml 3 pulls a vulnerable sprintf-js; the 2.x line is
# on js-yaml 4
esbuild: ^0.28.1
read-yaml-file: ^2.1.0
# Fourth wave. A caret on @tiptap/core alone floated to 3.31.x while
# @tiptap/react stayed on 3.22, which still imports cancelPositionCheck
# and schedulePositionCheck — exports 3.31 removed. Pin the family
# together on the patched line (prototype pollution <3.30.4, Markdown
# ReDoS <3.30.5).
'@tiptap/core': 3.32.0
'@tiptap/pm': 3.32.0
'@tiptap/react': 3.32.0
'@tiptap/starter-kit': 3.32.0
'@tiptap/extensions': 3.32.0
'@tiptap/extension-bubble-menu': 3.32.0
'@tiptap/extension-floating-menu': 3.32.0
'@tiptap/extension-image': 3.32.0
'@tiptap/extension-link': 3.32.0
'@tiptap/extension-placeholder': 3.32.0
# @tiptap/pm 3.32 wants prosemirror-model ^1.25.12 and prosemirror-view
# ^1.42.6, but schema-list/state still resolve an older line. Two copies
# make wrapInList throw, so list toolbar buttons no-op.
prosemirror-model: 1.25.12
prosemirror-view: 1.42.6
# auditConfig: advisories we have reviewed and decided not to fix. The weekly
# security-audit workflow honors this list, so an entry here also stops the job
# from re-proposing the same pin every week.
#
# braces (GHSA-vfj7-8cjw-p6xm, high) — the advisory names 3.0.4 as the fix,
# but 3.0.4 is not published on npm, so there is nothing to move to. Reached
# only through @changesets/cli's globbing over our own repository files.
# Review by 2026-11-22, or as soon as braces 3.0.4 is published.
auditConfig:
ignoreGhsas:
- GHSA-vfj7-8cjw-p6xm