Next.js + Supabase Starter Template (Prisma, Redux, Swagger)
The article discusses a Next.js and Supabase starter template created by Gazzel16, which aims to simplify the development process by providing a pre-configured setup for new projects. This template includes features such as Next.js API routes, Prisma, Supabase, and Redux, allowing developers to focus on building features instead of setting up the project from scratch. The template is open-sourced and available on GitHub, where users can clone, customize, and deploy it to Vercel and Supabase Cloud.
- ▪The template includes Next.js 16, TypeScript, and Tailwind
- ▪It features a layered backend with Prisma 7 and Redux Toolkit for client state and CRUD thunks
- ▪The template is deployable to Vercel and Supabase Cloud without a separate backend server
DEV.to (Top) files mainly under programming. We currently carry 4,924 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | DEV.to (Top) |
| Canonical URL | https://dev.to/gazzel16/nextjs-supabase-starter-template-prisma-redux-swagger-3khf |
| Publication time | Tue, 30 Jun 2026 08:05:03 +0000 |
| Retrieval time | 2026-06-30T08:24:24.649Z |
| Last seen | 2026-06-30T08:24:24.649Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | 3wqrf3gWjDyI |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
try { if(localStorage) { let currentUser = localStorage.getItem('current_user'); if (currentUser) { currentUser = JSON.parse(currentUser); if (currentUser.id === 4009206) { document.getElementById('article-show-container').classList.add('current-user-is-article-author'); } } } } catch (e) { console.error(e); } Gazzel16 Posted on Jun 30 Next.js + Supabase Starter Template (Prisma, Redux, Swagger) #nextjs #opensource #productivity #showdev Why I open-sourced this: I kept rebuilding the same setup for every new project — Next.js API routes, Prisma, Supabase, folder structure, and deploy steps. It was repetitive, and I wasted time deciding where code should live instead of building features.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at DEV.to (Top).
Discussion
0 commentsMore from DEV.to (Top)
