Rex E.

new navbar inspired by iOS 26 apple liquid glass ✨ 1: Before 2: After

an extra tab has been added to showcase how global state solves the problem in the same nextjs project: next-tabs.vercel.app

implementation is complete: react-router-tabs.vercel.app verdict: react-router does not automatically solve the problem of state persistence across routes what does solve the problem is a global state management solution next-js will live to see more days in this project 🤝

final decider will be if I can implement this in react-router with no hacks and have client state preserved through and through next-tabs.vercel.app

back. this close 🤏🏾 to migrating an entire project from next.js to react-router

@colinhacks Here’s a demo as well:

@colinhacks You could achieve a crude CMD+F across pages with an inverted-index of your site. I considered building this, but placed on hold for now! In the meanwhile here’s a blog post with a basic client-side implementation: rexforde.com/blog/react-fas…

and it's not particularly close

@rauchg looks great! Is this opt-in? And does it work with the Link component? This is a hack I put together to try to achieve persistent routes, but I think it should be easier? next-tabs.vercel.app

We're so back: navigation retains scroll position and content, even after 'load more' presses 😱

The new vercel.com/blog uses some cool @nextjs app router features: • shared persistent layout with animations • /changelog 'breaks out' of the /blog nav hierarchy

thinking out loud and may not be possible, but meta-programming? override process.env get() and only expose specific variables depending on place in stack trace at point of access. at least could be surfaced in logs so clear if anything is being accessed and then assessed later.

Your runtime environment variables are not safe. Just this code in an npm package would leak them to a malicious endpoint. So, where should you store your secrets?

@jal_eelll @nextjs Nice! I think the Promise.all call has to be inside the suspense boundary for this to work? Or is that wrong?

Easily one of my favorite data fetching pattern in @nextjs using RSCs. Parallel data fetching + streaming = fast UIs 🔥

I’ll share an article/snippet for anyone interested.

Realizing React.cache is like React.ref but for server components, while implementing per-request context for @featurevisor for easier DX in Next.js apps👌

and link to deployment app 🔗 next-tabs.vercel.app

here's the approach so far: github.com/rexfordessilfi…

hey @leeerob 👋🏾. how would you approach persistent routes in Next.js (similar to persistent layouts as we have today)? After searching, I put together a solution with Parallel Routes, and CSS `display` but it has a few rough edges. have any alternatives/tips for this? 🙏🏾

@webdevcody officially supercharged 😎

Frontend developers are officially cooked

@threepointone @genmon Yea. Most web apps should implement CMD+K support. It can be a huge productivity boost!

I met @genmon and he drew this for me and I haven't stopped thinking about it

@calcom embeds👌🏾

@thdxr how is linear able to so consistently identify and build these ux micro-behaviors and interactions? some you don’t even notice - just feel. others you stumble into just at the right place and time. we need some course/book/article on these at this point!

there's a detail in linear where it takes a second for a tooltip to open but once it's open other tooltips immediately show no one asked for this feature, it doesn't drive revenue - but if you claim to be committed to quality this is what you do, no questions asked

@devagrawal09 i feel (or felt) your pain before! what framework you using with it, and are you using CDK?

Why is setting up aws amplify such a big pain in the ass