2023-09-14
2823
#nextjs
Kapeel Kokane
141015
Sep 14, 2023 ⋅ 10 min read

Working with the Next.js 13 App Router

Kapeel Kokane Coder by day, content creator by night, learner at heart!

Recent posts:

the replay october 8

The Replay (10/8/25): Data enrichment, CSS is back, TypeScript 5.9

Discover what’s new in The Replay, LogRocket’s newsletter for dev and engineering leaders, in the October 8th issue.

Matt MacCormack
Oct 8, 2025 ⋅ 30 sec read
Goodbye, messy data: An engineer’s guide to scalable data enrichment

Goodbye, messy data: An engineer’s guide to scalable data enrichment

Walk through building a data enrichment workflow that moves beyond simple lead gen to become a powerful internal tool for enterprises.

Alexandra Spalato
Oct 8, 2025 ⋅ 6 min read

DesignCoder and the future of AI-generated UI

From sketches to code in minutes, DesignCoder shows how AI-generated, hierarchy-aware UIs could change the way developers prototype and ship apps.

Rosario De Chiara
Oct 7, 2025 ⋅ 5 min read

Should you use if() functions in CSS?

It’s 2025, and CSS finally thinks logically. The if() function brings real conditional styling — no hacks, no JS workarounds. Here’s how to use it right.

Ikeh Akinyemi
Oct 7, 2025 ⋅ 16 min read
View all posts

9 Replies to "Working with the Next.js 13 App Router"

  1. I don’t think “App” is production ready as the async jsx is not possible yet. dose it work for someone?

    const SubComponent = async () => { // <— async will cause promise error
    return async
    }

    export default function Sidebar() {
    return sidebar // <– this will error and die
    }

Leave a Reply