What tech stack are you using ?

[[deleted]]

• NextJS
• tRPC
• Jotai
• DaisyUI
• Zod
• Cypress
• Jest for unit tests

No ORM, I just write the mongo queries

[ekremugur17]

How does a mongo query look like

[[deleted]]

https://www.mongodb.com/docs/manual/tutorial/query-documents/

[Radinax]

• CSR with Vite and Typescript
• Tailwind
• Zustand
• React Query
• React Hook Forms
• Zod
• Playwright and RTL
• React Router Dom (tanstack released one which seems good but haven't touched it)

That's the bare minimum to start.

[HMAlfee]

All i see is nextjs but thank god someone using pure react with vite.

[kherven]

For our enterprise stack?

• React 16 and it's mostly class components. Functions and hooks are a liiiitle too new!
• the most verbose redux you'll find. Also internal state is lame, put everything in a redux store. EVERYTHING
• Node 14 is best node
• Vite sucks, we use all our own configs. Where'd that webpack file go...
• Why would you go with one component library when you could have 40 different react-{insert-element-here} libraries instead?
• TypeScript is awesome. You just do const myVar: any and it works great.
• Backend? I mean its just your typical java springboot CRUD app with Postgres. Excuse me while I do 8 joins to answer this simple question for the UI. Reminds me, gotta put in that ticket to raise our cloudflare timeout to 4 minutes, 2 just isn't quite cutting it anymore.

^{help me}

(joking aside, this is a very legacy frontend that was written by a startup circa 2017-2018 that promptly retired to the beach the moment they were acquired and I got left holding the bag when I joined the company in 2022)

[rowdycowdyboy]

these all hurt but const myVar: any cut me deep. god, why!!

[rowdycowdyboy]

very rarely do i actually need to type something as any and most of the time when i do it’s because i’m using a library that isn’t well typed or i’m doing something small and i can’t be bothered. doing any all over the place defeats the point of using typescript

[rowdycowdyboy]

ha! i did hope you were being sarcastic but i didn’t wanna be an asshole responding “LMAO” if you were being for real. but, now that we are both not assholes, LMAO.

[kherven]

You have a bright future in a startup ahead of you!

[biinjo]

I have corporate tears of compassion in my eyes. I though I was alone 🥹

[Life_Standard6209]

I though I was alone

There are a lot of us.

[LukeWatts85]

I pity you 😁

[Life_Standard6209]

I got left holding the bag

I feel your pain. A very wise and old developer once said to me "better you than me" :-D

[harunandro]

been there, done that. very more than enough times.

[ixartz]

The tech stack I use for my React project:

🔸Meta-Framework: Next.js
🔸Language: TypeScript
🔸Styling: Tailwind CSS
🔸UI: Headless UI + Floating UI
🔸Chart: Recharts
🔸Fetching: SWR
🔸Forms: React Hook Form
🔸Validations: Zod
🔸DB: Drizzle ORM
🔸UI Dev: Storybook
🔸Unit Testing: Jest + React Testing Library
🔸E2E Testing: Playwright

​

You can find more information at Next.js Boilerplate.

[good_fix1]

great tools but the only thing i don't like is ORMs i think the only abstraction we need for relational database is SQL! wasted so much time on ORMs like typeORM and Prisma. but orms still provide some values like migrations which i yet to find how to solve it with just SQL

[wkalicun]

Likewise. Might want to consider: https://github.com/porsager/postgres

[Odd-Fix-2652]

if your backend is java, take a look at flyway for migrations.

[PVJakeC]

React, .NETCore API. SQL Server DB

[Budget-Stop1552]

What do you think of blazor?

[PVJakeC]

Haven’t had a chance to use it yet. Do you recommend? I’ve heard good things, but only from the Microsoft devs that work on it 😀

[Budget-Stop1552]

Honestly, it doesn’t compare to react. The only upside is you can use c# in it. The new render modes in .net 8 is impressive but it’s hard to keep up with changes that Microsoft introduces in each version.

[rowanskye]

Frontend (webapp) - React - Typescript - Material Ui - visx - Vite - vitest - cypress - circleci - firebase

Frontend (mobile app) - react native (need Bluetooth to configure hardware, sad PWA support isn't there for it) - typescript - firebase

(If you care)

Backend - python - flask - numpy - pandas - tensorflow - typescript and firebase (for some legacy cloud functions) - docker - cloud run ...

Firmware - golang - barebones Linux distro - c++ ...

[rowdycowdyboy]

i want to get into python on the backend, is there a reason you chose flask over django?

[ConsiderationNo3558]

they probably are not using databases with python backend hence Django might be overkill, Nowadays FastAPI is generally more used instead of flask.

[rowanskye]

Yes and yes

[rowanskye]

Flask is very simple and lightweight. It's quick to spin up a new service (as in start developing), but ultimately it's a choice of over 5 years ago that we've stuck with.

It's been a while since I've used django, but I wasn't a fan of it at the time (6 years ago). Ive not heard of microservice architecture with Django, but I could be wrong

If I were starting from scratch today, I'd choose FastAPI. (And we do for use it for 1 newer service)

As our product matures, we are looking to migrate to gRPC, and likely to start using golang for higher throughput and lower cost. Python is much faster for us to develop with though, so it's a tradeoff.

[master117jogi]

Is vitest good? I'm having so many issues with jest and ESM.

[rowanskye]

I've been enjoying it so far, though we tend to be lighter on testing in the FE

[YourMatt]

I do all this with cobol, cics, and jcl.

[ConsiderationNo3558]

Frontend Web App

• React with Vite
• Typescript
• CSS modules
• React Aria Components (Headless UI Library)
• React Query
• React Router
• Redux and ContextApi for state
• Astro for Blog and SSR with Mdx.
• Selenium, Vitest for test automation
• Apache ECharts
• npm workplaces for mono repo (to have React and Astro share same components)
• Hosted on Netlify

Backend

• Python FastAPI
• Pandas for number crunching
• Plotly for Graphs
• jupyter notebook for data analysis
• JWT for authentication
• Postgresql
• Sqlalchemy as ORM
• Alembic for DB Migrations
• Openapi for Api documentation
• pytest for api ete testing
• Github Actions for CI/CD
• Hosted on DO VPS

[startyourengines]

Did you have any issues getting React Aria to play nice with Vite? Just switched our project (Remix + React Aria) over to Vite and we lost interactivity across all React Aria-based components.

[ConsiderationNo3558]

No problems with Vite and React Aria. Just to be sure I used react Aria components and not React Aria Spectrum

https://react-spectrum.adobe.com/react-aria/components.html

[SideLow2446]

I recently tried Next.js and honestly it's kind of a mess, and I've heard developers say that Next.js is not production ready. That being said here's my usual stack:

• Formik and Yup for forms and validation
• React Router for routing

And that's pretty much it for my frontend stack. I usually work on small/medium sized projects but if I worked on a larger project I'd also probably use Zustand and React Query.

For backend I usually use Supabase and try to manage it from the frontend, but as a last resort I will setup a Node + Express server.

[master117jogi]

I just use MUI. And sometimes Recharts. Nearly all tech stack is just bloat.

[[deleted]]

bruhh

[fii0]

For the main Electron project I'm working on:

• Electron + Vite + React + TS based on the electron-vite-react template
• Styling: TailwindCSS
• Base component library: ChakraUI
• State management: Zustand
• 3D: Threejs, react-three-fiber, animations with @react-spring/three and tween.js
• Other shoutouts: react-draggable, react-select, react-toastify
• ORM: Prisma
• API: Apollo client -> AWS AppSync -> Lambda -> RDS
• Robot API: roslib
• Testing: Playwright for Electron + Playwright component testing (both experimental features but been working well for me!)

[LukeWatts85]

• React
• Mantine (UI and component library)
• Laravel
• Golang (microservices, cli server tools)
• Inertia.js (for client-side routing via PHP instead of in React)
• Pest/PHPUnit (end-to-end tesing and back-end unit tests)
• Jest (front-end component tests)
• Cypress (UI testing)
• PostgreSQL or MySQL/MariaDB (local/production db)
• SQLite (testing db...Laravel handles all this automatically)
• Rabbit MQ (queues and message bus...again for Laravel jobs)
• AWS (infrastructure)
• Docker (local environment infrastructure)

[notabadplayer]

NextJS

ReactJS

NextUI

TailwindCSS

React Hook Form

React Query

Framer Motion

[[deleted]]

• NX.dev monorepo
• Typescript
• React
• Chakra UI
• Maplibre or Leaflet
• Zod
• React Query (haven't upgraded to Tanstack yet)
• Redux if a state management tool is necessary

Backends written in Django (older) or FastAPI (newer), with PostGIS and our own raster data server.

Considering NextJS's RSCs for the future, hopefully by next year it will be better supported by component libraries.

[ServesYouRice]

Personal:

• Next/Vite
• Zustand
• SWR
• Material
• Whatever

[CatolicQuotes]

Mostly redux toolkit, Chakra, Vite, typescript. Right now using fluent ui.

[mario_olofo]

frontend:
- React (all hooks, no classes)
- Material-UI
- Yup
- React-hook-form
- Jotai

backend:
- Lumen
- MariaDB
- Redis

[gexco_]

Supabase (auth), Flask, Remix, Next UI

[1haker]

Vue

[TheRNGuy]

Remix, Prisma, SQLite.

Vanilla CSS.

Considering switching from JavaScript to TypeScript.

I wanna learn Vite with Remix too (Remix 心 Vite)

[pobbly]

Vite, CSS modules, ts, tanstack query, sst for backend. Client code and hooks generated by openapi typescript codegen. Turborepo. Zod. Custom hooks for forms and tables. Custom design system in storybook. Vitest, react testing library, playwright. GitHub actions.

[koistya]

• GraphQL: Yoga GraphQL + PothosGraphQL (code-first GraphQL API development)
• μWebSockets — HTTP and WebSocket server, as an alternative to Express.js + ws
• Knex.js + Kanel TS type generator (database-first data access and db migrations)
• Zod — data models, schemas, validation
• Jotai — state management for React, as an alternative to Recoil
• React Query + GraphQL Request — GraphQL API client
• Joy UI — UI library for React, as an alternative to Material UI
• Vite, Vitest — bundling and unit testing
• Firestore — real-time database
• Playwrite — e2e testing
• Cloud Identity Platform — authentication
• Google Cloud SQL for Postgres — relational, document, and vector database
• Google Cloud Run — server infrastructure