DX Engineer. Building with Next.js and React.
You're following everyone we can think of. Browse tags to find more people.
I'm a bit confused about this. Why does Next.js seem to make this use case so complicated?
If my backend is completely separate from my frontend, do I still have to use Server Actions or API Routes just to hide the backend endpoints from the client?
If not, is it perfectly fine to use Next.js essentially as React and call my backend APIs directly from the client? Am I missing something?
Open-sourced the project starter I reach for on every new app. Sensible defaults, a folder layout I trust, and a checklist of the things I always forget to set up. Fork it and make it yours. #opensource
Open-sourced the internal dashboard kit we've been using at work. Six components, no dependencies you don't already have. The docs are rough but it's all there. Use it, break it, and tell me what's missing. #opensource
Releasing `create-next-kit`, the CLI I built for spinning up Next.js 16 apps with caching, server actions, and a folder structure already wired. One command to a deployable app. #opensource
This Drop is intentionally long.
Added formatting to the Drop composer. You can write bold, italic, and code blocks now, and there's a Preview toggle so you can check a drop before posting. The preview renders on the server with the same component the feed uses, so it matches exactly. Try it and tell me what breaks. #shipping
The following feed in Drop is cached per user and invalidated on write. It comes down to one `'use cache'` function with a tag: #opensource #nextjs
const data = { name: "asd", count: 123 };terwtenpx create-next-kit my-app
cd my-app
pnpm dev<Link href={href} prefetch={true} />async function getFeed(handle) {
'use cache'
cacheTag(`feed-${handle}`)
return db.drops.forFollowing(handle)
}