Ecommerce Template
Modern ecommerce template built with Next.js 16, React 19, Drizzle, Better Auth, Supabase, and Stripe.
Company equipment catalog & store buildout configurator
Translation pending
CommerceTypeScript · PythonGitHub @cwhweihuanOnlineOwner 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
The maker's introduction consists of the line above. Read the repository README for more details. Repository README ↗
Loading the full README.
Read the full README ↗A web app for archiving company equipment and configuring store buildouts. It replaces a sprawling master spreadsheet with a searchable catalog of equipment "cards" (each with specs and a spec-sheet PDF) and a drag-and-drop builder for assembling the equipment list of a new store.
| Layer | Tech |
|---|---|
| Framework | Next.js 16 (App Router) + TypeScript |
| UI | Tailwind CSS v4, lucide-react, dnd-kit |
| Data | Supabase Postgres via Prisma |
| Files | Supabase Storage (spec PDFs) |
| Export | exceljs (Excel) + jszip (PDF bundle) |
| Hosting | Vercel |
npm install
cp .env.example .env # fill in your Supabase credentials
npx prisma migrate dev # create tables
npm run db:seed # load 209 items, 3 sample stores, upload PDFs to Storage
npm run dev # http://localhost:3000
The original data lived in a Google Sheet (master list + per-store tabs) with spec PDFs
hyperlinked from Google Drive. data/extract.py parses the exported workbook into
data/seed/*.json; the spec PDFs are downloaded from Drive and re-hosted in Supabase Storage
by the seed script.
Set the same environment variables from .env.example in the Vercel project. The build runs
prisma generate && prisma migrate deploy && next build, so schema changes apply on deploy.