Searchcaster

welter.eth@fun

9/1/2023

noob question, how should i be setting up my next.js directory when i get to this part? does it matter? tagging ppl for help @greg @pixel @matthew @stephancill

vincent@pixel

9/1/2023

Not an expert on Next.js, Greg uses it a lot :)

Brian Kim@brianjckim.eth

9/1/2023

i use the same as above except i add import aliases

Greg@greg

9/1/2023

It’s personal preference but I go yes yes no yes no (should probs be yes) no

pugson@pugson

9/1/2023

don’t use eslint

Brent Fitzgerald@bf

9/1/2023

> does it matter? recommend avoiding this question when developing because it leads right into a nihilism abyss.

Matthew@matthew

9/1/2023

eh I wouldn't use tailwind

Uncle Davo@uncledavo

9/1/2023

diving into next.js soon too! will join u w the noob questions 🫡

dinislam@dinislam.eth

9/1/2023

my complaints for app directory: - no way to return non-200 responses in server components - cookies are some times read only (i forget if that’s in server components or routes) - no good CSP solution that I’ve seen I’m coming straight from CRA, never used Pages router

timdaub (🥝,👄)@timdaub.eth

9/1/2023

me: - ts? no - eslint: no - tailwind: no - wtf does that mean? - router: no - wtf does that mean

one of the many matts@1ofthemanymatts

9/2/2023

defaults are the move. if you don't like tailwind at first try using shadcn/ui's patterns and see if you still hate it. don't listen to the devils on your shoulders telling you to remove eslint, if anything add more eslint rules (like package sorting) and also prettier plugin. then never manually format code again

matthias@iammatthias

9/2/2023

yes yes no yes yes no