What's your current tech stack for web dev?

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.

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.

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

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 :)

Really interesting.
Thanks for sharing!

Next.js, SWR, Supabase, Chakra UI.

NATS:

• Nuxtjs
• Apollo
• Tailwind
• Storefront API

MERN Stack

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

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!

Django, HTMX, PostgreSQL, Tailwind

Frontend: React, Vue
Backend: Laravel, Express, Nestjs, .NET Core
Database: MySQL, PostgresSQL
Deployment: Heroku, Digital Ocean

Astro, Vue 3/TS, Pinia, Vite, Tailwind
Laravel, GraphQL, MySQL

Web Components with Lit/TS, OpenWC

Frontend: Angular 13, Tailwind CSS, NgZorro
Backend: ASP.Net Core 6, Dapper, EF Core
Database: PostgreSQL, MSSQL
Hosting: AWS, Azure

Node.js, PostgreSQL, PostGraphile, Redis, Next.js, Bootstrap css, knex.js, Prisma, Amazon SES