Ecommerce Template
Modern ecommerce template built with Next.js 16, React 19, Drizzle, Better Auth, Supabase, and Stripe.
Plan your week, price it at Tesco, Sainsbury's, Asda or Waitrose, and we'll order the missing ingredients to your door.
CommerceJavaScript · HTMLGitHub @NoeBouchardOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Loading the full README. The saved excerpt is shown below.
Your kitchen on autopilot. A concierge grocery + meal-planning app (HelloFresh alternative). Customer pays Plentry via Stripe; Ops shops at Tesco / Sainsbury’s / Asda / Waitrose; 5% fee.
• Live: https://getplentry.com
• App: index.html + supabase/functions/ — no React, no Next, no bundler
• Product truth: doc/ (copied from the workspace vault). Start at doc/REQUIREMENTS.md.
• Tests: npm test must exit 0 before any production deploy. GitHub Actions test is the merge gate. Vercel is not git-connected; git push / merge does not ship the site. See doc/ENGINEERING.md.Read the full README ↗Your kitchen on autopilot. A concierge grocery + meal-planning app (HelloFresh alternative). Customer pays Plentry via Stripe; Ops shops at Tesco / Sainsbury’s / Asda / Waitrose; 5% fee.
index.html + supabase/functions/ — no React, no Next, no bundlerdoc/ (copied from the workspace vault). Start at doc/REQUIREMENTS.md.npm test must exit 0 before any production deploy. GitHub Actions test is the merge gate. Since PR #12 (15 Oct 2026) a merge to main does not auto-deploy static. Deploy to production is OFF, so a merge does not deploy edge functions either. Functions deploy only by hand with supabase functions deploy <name> or MCP, under a GO. If Deploy to production is ever re-enabled, every merge redeploys all functions. Production static is the REST create and promote in doc/RUNBOOK.md. See doc/ENGINEERING.md.supabase/migrations/. Files there would auto-apply to prod on merge via the Supabase GitHub integration.Do not implement from historical drafts. Those live in doc/archive/ in the workspace vault.