next.js 13 app router no longer supports <Head> so you gotta jump through hoops to set metadata on pages with 'use client' 😩

🔍 ensdata.net ✦ 🖼️ pugson.net/rfe ✦  🌐 metadata.vision ✦ 𝙽𝙾𝚆: design engineer @family ✦ 𝙿𝚁𝙴𝚅: @rainbow 🌈

✳︎ design engineer → @ponder 
✳︎ explorer of humanism • petrolhead/gearhead
✳︎ React/SwiftUI
✳︎ bento.me/matthew

this doesn’t work on ‘use client’ components

You don't have to. You can use `generateMetadata` directly server side in Next.js 13.4 with App Router.

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

i’ve been using it with expo router for unlonely mobile and it’s pretty sweet. 

wanted an easy setup for intercepted and parallel routes for this project. collocation of one-off components and assets only used in that route is really awesome for organizing your repo.

what made you want to use app directory vs normal next.js stuff? I feel like I've heard more downsides than upsides recently

𝓵𝓲𝓿𝓲𝓷𝓰 𝓽𝓱𝓮 𝓮𝓷𝓭𝓵𝓮𝓼𝓼 𝓼𝓾𝓶𝓶𝓮𝓻 • building @buoy 🛟 • skeet.build • pfista.com

you can. but i’m talking about client components

I thought you could still set metadata on server components by exporting the const, did they take that away or was it never a thing

yeah very annoying. this is my current solution. using an additional layout that wraps the page that has 'use client'

oh no

isn't one of the main features of next.js better head management than spa apps?

😂