What's your stack?

So I asked chatGPT to list my core "AI-assisted coding" stack items and what they are and it went waaaay overboard. I think it thinks I'm a moron.

What's your stack? Is the below stack really the best combination (chatGPT seems to think so)? If anybody wants to add their stack in the comments, maybe just do it in one line, like chatGPT did right at the end: myStack=TypeScript + React + Next.js + Tailwind + Supabase + PostgreSQL + Vercel with Tauri added when I want a desktop app.

The core stack items

1) JavaScript

What it is: The core programming language of the web.


Used for: Frontend and backend code.


Think of it as: The foundation everything else sits on.

2) TypeScript

What it is: JavaScript with static typing.


Based on: JavaScript.


Used for: Safer code, better autocomplete, fewer silly mistakes.


Think of it as: JavaScript with guard rails.

Rule of thumb: TypeScript is usually the better default for app projects.

3) React

What it is: A UI library.


Based on: JavaScript / TypeScript.


Used for: Building screens, components, forms, dashboards, and reusable UI pieces.


Think of it as: The system for building the visible parts of an app.

4) Next.js

What it is: A full-stack framework built on React.


Based on: React.


Used for: Routing, layouts, server-side logic, app structure, and production-ready web apps.


Think of it as: React plus the app framework around it.

Simple view:


React = components


Next.js = complete app structure

5) HTML

What it is: The structure of web pages.


Used for: Markup and page content.


Think of it as: The bones of the UI.

6) CSS

What it is: The styling language for the web.


Used for: Layout, spacing, colours, typography, responsiveness.


Think of it as: The visual design layer.

7) Tailwind CSS

What it is: A utility-first CSS framework.


Based on: CSS.


Used for: Fast, consistent styling directly in components.


Think of it as: A quicker, more structured way to style apps.

8) Node.js

What it is: A JavaScript runtime for running code outside the browser.


Based on: JavaScript.


Used for: Dev servers, build tools, package scripts, backend code.


Think of it as: What powers the development/tooling side of modern JS apps.

9) npm / pnpm

What it is: Package managers for the Node.js ecosystem.


Used for: Installing libraries and running project scripts.


Think of it as: Dependency management for JavaScript projects.

10) Supabase

What it is: A backend platform / BaaS.


Based on: PostgreSQL.


Used for: Database, auth, storage, APIs, realtime features.


Think of it as: A ready-made backend platform for modern apps.

Important distinction: Supabase is not the database language. It is a platform built around PostgreSQL.

11) PostgreSQL

What it is: A relational database.


Based on: SQL.


Used for: Storing structured application data.


Think of it as: The actual database engine underneath Supabase.

12) SQL

What it is: A query language for relational databases.


Used for: Reading and writing data.


Think of it as: The language used to talk to PostgreSQL.

Easy chain to remember:


SQL → language


PostgreSQL → database


Supabase → platform built around PostgreSQL

13) Auth

What it is: Authentication and user access control.


Used for: Sign in, sign up, passwords, roles, permissions.


Typical provider in this stack: Supabase Auth.


Think of it as: User accounts and access rules.

14) Vercel

What it is: A hosting and deployment platform.


Used for: Publishing Next.js web apps.


Think of it as: Where the app lives online.

15) Tauri

What it is: A desktop app wrapper/framework.


Based on: A web frontend plus a Rust native layer.


Used for: Turning a web app into a Windows/Mac/Linux desktop app.


Think of it as: The desktop shell around a React/Next-style app.

16) Rust

What it is: A systems programming language.


Used for: The native/backend layer in Tauri apps.


Think of it as: The engine under the bonnet of the desktop wrapper.

17) SQLite

What it is: A lightweight embedded SQL database.


Based on: SQL.


Used for: Local desktop storage.


Think of it as: A simple local database when you do not want a full cloud backend.

18) JSX / TSX

What it is: React file syntax.


Based on: JavaScript / TypeScript plus HTML-like markup.


Used for: Writing React components.


Think of it as: The format React code is usually written in.

The default stack combo I’ve mostly been using

Web app / SaaS

• TypeScript


• React


• Next.js


• Tailwind CSS


• Supabase


• PostgreSQL


• Vercel

Desktop app

• TypeScript


• React


• Tailwind CSS


• Tauri


• Rust


• 
  SQLite or Supabase/PostgreSQL
  

The plain-English mapping

• 
  JavaScript = programming language
  


• 
  TypeScript = safer JavaScript
  


• 
  React = UI building system
  


• 
  Next.js = full web app framework
  


• 
  Tailwind = styling approach
  


• 
  Supabase = backend platform
  


• 
  PostgreSQL = relational database
  


• 
  SQL = database query language
  


• 
  Vercel = hosting
  


• 
  Tauri = desktop app shell
  


• 
  Rust = native layer under Tauri
  

TL;DR

If I had to summarise the core modern vibe-coding stack in one line:

TypeScript + React + Next.js + Tailwind + Supabase + PostgreSQL + Vercel


with Tauri added when I want a desktop app.