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
Build the seller panel before the E2E suite runs
Damian Legawiec3fcca7b7e302
diff --git a/.github/workflows/packages.yml b/.github/workflows/packages.ymlindex 448b61957a..6aae39b9ce 100644--- a/.github/workflows/packages.yml+++ b/.github/workflows/packages.yml@@ -144,8 +144,13 @@ jobs:# SPA (`vite preview`, E2E_PREVIEW below): fresh browser contexts have# empty caches, so the dev server would re-serve hundreds of on-demand# modules on every page load in every test.+ #+ # The seller panel is served alongside it, because accepting a seller+ # invitation happens there rather than in the dashboard. Its starter's+ # vite config imports `@spree/seller-dashboard/vite`, which resolves to+ # that package's `dist/`, so it must be built even to load the config.- name: Build dashboard packages- run: pnpm turbo build --filter=@spree/dashboard --cache-dir=.turbo+ run: pnpm turbo build --filter=@spree/dashboard --filter=@spree/seller-dashboard-starter --cache-dir=.turbo- name: Setup dummy Rails appworking-directory: spree/api