What's your current tech stack for web dev?

Tech Stacks, the complete package of tools needed by a web developer to create an awesome web app. A single web app can be made using many different teach stacks, it completely depends on the developer and on the developer trends. So, what's your current tech stack? It can have frameworks, databases, ORMs, CSS frameworks, tools and literally anything you use in the development process. Don't forget to give them weird abbreviations 😂

My current tech stack is NPTS which sounds weird,

• N stands for NextJS, framework.
• P stands for Prisma, ORM.
• T stands for Tailwind, for styling.
• S stands for Supabase, database.

It's a frontend focused tech stack.

Comments

[Amr Elmohamady]

Frontend:

• Vue for SPA
• Vuex for state management
• Nuxt if SSR or SSG is needed
• Vuetify for UI components
• Tailwind if I can't use vuetify (material design)

Mobile:

• IonicVue I don't do Mobile but if I needed Ionic now supports Vue
• capacitor for native things

Backend:

• Nodejs
• Nestjs (not Next.js) is a super cool framework for Rest, GraphQL, WebSockets and Microservices that is built on the inversion of control principle using dependency injection built on top of express and fastify
• Express if I can't use nestjs
• TypORM is a solid ORM
• Sequelize when not using typescript

Database:

• Postgres is my first choice for DBMS
• MySQL is the company choice not mine
• MongoDB when NoSQL is needed
• Redis as centralized store for sessions and rate limiting tokens, for caching and for pub/sub WebSocket servers communication.

[ashish]

pretty clean stack, I have tried using vuetify with vite, does it support vue 3?

[Amr Elmohamady]

Not yet, it is currently in beta :(

[ashish]

I see, hope that they release stable version soon, thanks for letting know

[Marco Colli]

For Pushpad we use Ruby on Rails with PostgreSQL and Redis, plain CSS and JavaScript and we deploy on custom infrastructure on DigitalOcean.
For BuonMenu it's the same, but we deploy on Heroku, since it's a smaller website.

[ashish]

both look great, specially liked the buonmenu app, great concept ❤

[Marco Colli]

Hey, Thank you :)

[Guilherme Tavares]

I'm planning to be a Node.js/.NET Core Fullstack Developer, so:

• JavaScript, TypeScript and C#
• React, Next.js and Gatsby (sometimes Angular 2+)
• Node.js (Express or Nest.js) and ASP.NET Core
• MSSQL, PostgreSQL and MongoDB / Prisma and Entity Framework Core
• Microsoft Azure

[Iván Torres García]

Well I'm currently learning so I usually change the tech but:
Front: VueJS 3 (ViteJS) + TS + Windicss
Back: Express + TS + MongoDB (Should I give a try to NestJS??)
Devops: Docker + Actions
Testing: Vitest + Testing library + Cypress

Happy to hear if sb could give me some advise or some tech to start to use :)

[ashish]

vitest is great!

[StormyTalent]

Really interesting.
Thanks for sharing!

[ashish]

thanks ❤ waiting for more people to share their stacks, can't wait to see some unique stacks!

[StormyTalent]

Next.js/Gatsby.js
Node.js/Express
Django
Web3/Solidity
:-)

[StormyTalent]

I am really interesting on you.
Could I get your address? That we can have communication for our development?
Thanks!

[ashish]

sure, if you're on discord you can contact me there, my id is asheeshh#7727 or you can contact me on twitter @_asheeshh

[StormyTalent]

Hmm.. I don't use both of them.
Do you use Slack?
My ad2r is "icefoxteny gm com"
Please send me invitation.
:-)

[O. AlQudah]

Next.js, SWR, Supabase, Chakra UI.

[ashish]

one of my fav stacks 💪

[Josh Corbett]

NATS:

• Nuxtjs
• Apollo
• Tailwind
• Storefront API

[Zelal Hossain]

MERN Stack

[Zain Ahmed]

Fronend : React | Tailwind
BackEnd : Node.js | Firebase
Database : MongoDB

[Nik F P]

I've been working in a monorepo structure with:

• Front end: Svelte with native CSS and handrolled Grapqhl library

• Back end: Postgres with Prisma > Fastify > Graphql built out with Envelop and Graphql-modules

• A shared code library that houses type definitions generated by GraphQL Codegen, as well as common code like input validations and a few helper functions that are needed on both sides of the wire

I've also been working on a hobby project using;

• Sveltekit as the whole stack, using KitQL for graphql on the client portion, and Envelop, Graphql-Modules, and Prisma in the endpoints. Graphql-Codegen generates the types for all of this, as well as the KitQL client. This is set up to work in a serverless environment and will point to Supabase when deployed.

Looking at this and thinking about it in context, it's amazing how much productivity I've gained through the use of projects from just 2 organizations.

• Prisma is just awesome. Full stop.
• The Guild and their extensive ecosystem of tools surrounding Grapqhl is just extraordinary. No Apollo lock in for me!