It’s Next.js Liberation Day.
The #1 request we kept hearing: help us run Next fast and secure, without the lock-in and the costs.
So we did it. We kept the amazing DX of @nextjs, without the bespoke tooling, built on @vite. We’re working with other providers to make deployment a first-class experience everywhere.
Next.js belongs to everyone.
https://t.co/2A3pHnQLfp
@Baconbrix@mark__lawlor@expo What is in my mind is shadcn ui is becoming more and more dominant on frontend and maybe an abstraction can be created on top it. I mean a spec by shadcn ui can be useful for native as well. Already implemented by shadcn for web and it can be great a counterpart in react native.
New components. This time it’s the boring stuff. The things we rebuild over and over. Made into components.
Button Group, Field, Input Group, Empty States, Item.
They compose beautifully and handle the common patterns we reach for every day.
Let’s take a look ⬇️
@Baconbrix Almost all AIs think that Expo Router supports [id].tsx, [[id]].tsx, [...id].tsx, [[...id]].tsx . How can this be? Expo Router has ever supported these?
I ended up something very similar to you. You come up from AI perspective whereas my concern is readability. This feature based approach is much more readable. Would you please share your cursor rules? If you can end up with a nice documentation we may collaborate on this together.