I’m using shadcn/ui in a production app and adapting the base components to match our Figma design system. I’m a bit stuck on how people usually handle scaling this setup.

Issues I keep running into:

- some components depend on Button variants/sizes (ghost, sm, icon, etc), so changing/removing them breaks other components (Calendar, DatePicker, etc)

- if I keep everything, I end up with a bunch of unused variants/sizes that don’t actually match our design system

- I need to introduce our own variants, but naming overlaps are already happening (same names, different visual meaning)

- changing base styles via tokens only goes so far and eventually I need real overrides

- once files are customized, updates become unclear (not sure when people actually merge upstream changes vs just stop updating)

- also not sure when it’s better to modify the base shadcn components vs wrapping them

So it feels like I’m choosing between a few imperfect options: keep shadcn mostly as-is, fork it, or build a wrapper layer on top - but none of them feel obviously “correct” for a production app that will actually evolve.

How are people handling this in real, maintained codebases?

Shipped a side project — a résumé roaster/rewriter — and the Next.js decisions were the interesting part:
• App Router, everything server-side for the AI calls
• No auth at all — land, paste, result in 30s. Killing the sign-up wall roughly doubled how many people reach first value in testing.
• Because there’s no auth, résumés are processed in-session and never persisted — privacy stance falls out of the architecture for free
• Anthropic API for generation, streamed back to the client
• Razorpay for the paid tier, deployed on Vercel
Happy to go into how I structured the streaming + the no-auth payment flow if useful. Anything you’d have done differently?

I'm curious how many people are successfully running Next.js outside of the Vercel ecosystem.

I recently moved my project to:

• Cloudflare Pages
• Cloudflare Workers

while replacing Supabase with Turso and WorkOS.

For those who have done something similar:

• Any compatibility issues?
• Any performance differences?
• Would you go back to Vercel?

I'd love to hear your experience.

Currently, I am developing a desktop app that works with a drag-and-drop and blueprint logic, allowing users to build Next.js applications. The core concept started with the idea of creating a tool for full-stack web application development by combining the design aspect of WordPress with the blueprint system of Unreal Engine. I am currently close to completing the MVP, but I would love to get your feedback. Let me explain the basic working principle to you.

On the design side, components work using a drag-and-drop method. You can customize the components as you wish, assign classes, or modify predefined properties. Essentially, you can also use components and themes prepared by other developers within a marketplace.

On the blueprint side, you can manage both the JS functions to be used on the client side and the functions to be used on the server side using a drag-and-drop system.

Architecturally, because it processes and stores all components, pages, functions, and other data as JSON files during the development phase, it runs very fast. At the same time, when the project is exported, it is exported just like a standard Next.js project and can be uploaded to GitHub or similar platforms. Additionally, other Next.js projects can be imported into the system. I don't have any plans to include AI support at the moment, but I might consider it for future versions.

What I am specifically wondering is this: I am running this project as a hobby with no financial expectations, but is it worth it? My goal is to enable people who don't know how to code to develop web applications, while also aiming to increase the efficiency of engineers. I can share screenshots if anyone is interested.

Hey,

So I studied full stack web development and I'm backend oriented.
I created a shift management app for my manager in the security company I work as a guard.
I did it with the meta stack, that most of the companies work with:
- JS / Node.js - focused on fundamentals
- Next.js / React - full stack apps
- TS / Zod / RHF / pg / ShadcnUI /Better-Auth/Neon/Prisma etc

Every single day for almost a year, I did 30 minutes of recalls while improving answers bit by bit, then 1:30 of study sessions, then building projects.
I started doing mock technical interviews with Claude/GPT, and I'm able to pass them and talk about each concept a lot.

Right now, it work on the building I work at, and this week we are expanding to 2 more buildings, and soon to 10-20 more.

I also collected data of 3000 urls of career pages of companies, created a node scraper with Claude Code, it matches around 4-5 open roles in a week. But for each one of them, probably 100+ people sent their cvs so I cannot get even an interview.

I barely see open roles for Juniors, and I'm someone who is fast with computers (used to be a heavy gamer) and I feel like I made a mistake and spent a lot of time studying something that is not required anymore.

I live in Israel, which is considered the startup nation, with the highest rate of startups for the amount of the population, and yet no open roles, many people are being fired.

Should I stop and start another chapter in other place and not in developing?

Was that problem ever resolved?

If I want to render on the server, can I still useContext?

I'm building a dashboard with Next.js (App Router) as the frontend and a separate FastAPI backend. Authentication is handled by the backend, while Next.js stores the JWT in a secure httpOnly cookie and acts as a BFF.

Now I'm adding role-based access (admin and user). What's the recommended architecture for handling page protection in this kind of setup?

Should Next.js verify the JWT locally (using the shared public key/secret), call the backend to validate roles, or rely on another approach? What's considered the best practice when using a separate backend?

I’m working on a consumer fintech idea around spending abroad.

The first version would let someone look back at their foreign card transactions and see where they may have lost money through bad exchange rates or DCC, and which of their cards performed worst.

My main worry is that the first reveal might be interesting, but only once. Someone sees the number, thinks “that’s annoying,” and then never opens the app again.

The more useful version would probably help during future trips by flagging expensive charges and telling people which card would be better to use next time. That sounds stronger, but it also means building a lot more before knowing if people actually care.

How would you test the repeat-use side without overbuilding it?

I was thinking of looking at whether people come back before another trip, turn on alerts, or check which card is best for a destination. Curious what other signals or small experiments you’d use before investing too much into the full version.

Hi all,

I am building a new app in Next.js and Prisma, because I saw the hype online.

My previous application was raw SQL, which was fine, and I could use promises of types to help with type safety.

So, in my new project I have two files

types.ts

schema-prisma.ts

Let's say I have a type of Book

export type Book { id: string, pages: number; title: string }

Then, you have the same in Prisma to store books

Model Book { id: string , pages: number; title: string }

So, the second you make a change to your type of Book, like adding new data or making something null, you need to go back into the prisma schema to make it match.

What should I be doing?

AI suggests to delete types.ts and use the schema prisma as the types, is that correct?

Hello, I'm using clerk for my new projects and the am also okay with switching to the pro plan. However, I see no way to collect additional information after sign up. For example, I would like to add a phone number collection request after Google sign up (I know if it offers phone authentication separately but most people prefer login using Google on desktop). Also, is there any way for them to provide additional information like the industry they belong to? If there's no default option, is there any feasible workaround which can achieve this?

If you are building a data table, with pagination and sorting, do you use server components, with page reloads per sort/pagination click, or do you make the table client side, with API calls for the data loads?

I can see pros and cons of both.

Curious what people doing?

Would be great to hear the reasons for your choice also.

Hey everyone,

For the last 6 months, I’ve been building ReCode, a dedicated AI web workbench for developers. But because I've been building in a silo, I need a brutal reality check.

I know inline IDE tools like Cursor and Copilot dominate right now. But my goal was to build a separate environment specifically for boring, multi-step tasks that usually clutter up an IDE chat tab. It also doesn't store any of your code (processed in memory) so isnt a vibe coding tool at all.

Here is what it handles right now:

Mock Data Factory: Parses your SQL/Prisma schemas and generates complex, relational mock data with proper foreign key mapping.

Code Auditor: Runs a deep health check for architecture smells, security flaws, and visualizes Big O complexity.

Universal Translator: Accurately migrates logic and whole files between languages (like Python to TS, C++ to Rust).

And there are more tools but they are less important.

My Dilemma:

I know developers hate breaking their flow.

Is context-switching to a standalone web app a total dealbreaker for you?

Would you ever use a separate tool for complex tasks like DB seeding or deep code audits, writing boring RegEx, translating CSS between its frameworks and so on, or is your IDE chat genuinely enough?

If I need to swallow my pride and pivot this into a VS Code extension, tell me. Be brutal. I’ve attached a few screenshots so you can see what the UI looks like. Thanks!

P.S. If anyone actually wants to poke around the UI and tell me why it sucks, the alpha is live here: recode-alpha.vercel.app

I'm building an video platform and right now it lives in 4 separate repos:

1. Main web app — React (TanStack Start), deployed on Vercel
2. Admin dashboard — also React/TypeScript, internal tool
3. API backend — Python FastAPI + a Redis worker, deployed on AWS/Railway
4. Video pipeline — Python, runs on AWS Lambda

They all talk to the same Supabase (Postgres) database and Redis, and they call each other. The database migrations live in the main web app repo, but the Python services read the same tables.

The pain points I'm having:

• When I change the database schema, I have to update types/models in multiple repos by hand and keep them in sync.
• A single feature often means opening PRs in 2–3 repos at once.
• Shared config (env vars, API contracts) drifts between repos.

My question: is it worth moving all of this into one monorepo, even though it's mixed TypeScript + Python with completely different deploy targets (Vercel, AWS Lambda, ECS)? Or is the mixed-language, mixed-deployment situation exactly when you should NOT do a monorepo?

If you've done this — did tools like Turborepo/Nx/Pants handle the Python side okay, or did you just use a plain monorepo with separate CI workflows per folder? Any regrets either way?

Solo dev / small team, so I care more about "less friction day to day" than big-org tooling.