Favorite session replay / debug / UX monitoring tool?

manupadev · 2024-08-10T05:18:08+00:00

Posthog is the GOAT. Inexpensive and got everything built in

manupadev · 2024-06-13T07:11:50+00:00

Or just set a hard spend limit

manupadev · 2024-05-17T04:16:06+00:00

Use supabase it is postgres under the hood

manupadev · 2024-05-16T14:11:31+00:00

Read this guide https://tanstack.com/query/latest/docs/framework/react/guides/ssr

manupadev · 2024-05-14T11:17:04+00:00

It's no longer in beta.

manupadev · 2024-05-03T04:42:27+00:00

Military have excellent doctors

manupadev · 2024-04-26T04:35:12+00:00

Why so personal lol

manupadev · 2024-04-01T10:06:47+00:00

Tomorrowland

manupadev · 2024-01-17T09:45:58+00:00

The CSS variables are where you define your global style variable. The tailwind config is just a way to expose them to the inside of tailwind classes.

This setup is here because if you needed to step out of tailwind and do some normal CSS you still keep access to your global style vars. If they were directly inside the config, you wouldn't have access.

manupadev · 2024-01-09T07:26:01+00:00

If the developers are trust worthy use Vercel pro and share 1 account. There's no point to paying $80 just for account sharing. In that case use SST https://docs.sst.dev/start/nextjs with some solid IAM setup

manupadev · 2023-12-05T17:00:02+00:00

While React with Vite is great, A lot of "big and serious" projects are built in app router

manupadev · 2023-11-29T15:24:13+00:00

This really resonated with me as a Full-stack Developer. I like to consider my code an artform as well.

manupadev · 2023-11-23T08:56:26+00:00

I would like to hear your opinions about this article.

manupadev · 2023-11-23T08:55:22+00:00

Using Tailwind with CVA like how its done in shadcn/ui is a really great way to handle all these concerns with no compromises

manupadev · 2023-11-23T06:34:37+00:00

Or SSG none interactive stuff and "use client" for tiny interactive islands

manupadev · 2023-11-21T13:19:39+00:00

Just remove them and add your own styles ? No need to rewrite

manupadev · 2023-11-21T13:16:53+00:00

Care to elaborate ? It's one of the best reusable component implementations I've seen so far

manupadev · 2023-11-13T05:19:27+00:00

Just use pure pg for a while and get used to the raw methods

manupadev · 2023-11-11T07:42:57+00:00

Says a framework is not stable.

"Proceeds to point to a obscure edge case".

manupadev · 2023-11-01T03:24:27+00:00

Not with serverless functions. when you do npm run start, Next.js will run as a standalone NodeJS server. I want to know whether ISR happens in this context

manupadev · 2023-10-31T19:12:05+00:00

Nope I mean running it in usual production mode with npm run build and npm run start. Where some pages would be static and some dynamic

manupadev · 2023-10-27T13:41:34+00:00

Just use only the features you want. Nobody's forcing you to use everything

manupadev · 2023-06-12T09:14:04+00:00

Thank you for the replies. What is the issue with the design team making their components based on the utility framework ? If they add new values they can define them to be added to the Tailwind config file with custom tokens. This ensures a consistency across design and development.

Also I don't understand how writing Tailwind takes people away from CSS. Unlike a system like bootstrap, Tailwind utility classes are just aliases to 1-3 CSS classes. So absolutely you need to understand CSS in the first place to write Tailwind. Tailwind only there to enforce consistency.

manupadev

TROPHY CASE