Content pfp
Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions

welter pfp
welter
@fun
next.js 13 using app router if you can help with any of these, that would be greatly appreciated – pre-load skeleton of site as content loads – show nprogress bar on top of page as content loads – disable button if input has no value
5 replies
0 recast
2 reactions

matthias pfp
matthias
@iammatthias
I have a rough skeleton working locally with this pattern right now. Trying to get it figured out for myself as well… https://nextjs.org/docs/app/building-your-application/routing/loading-ui-and-streaming
1 reply
0 recast
0 reaction

Elie pfp
Elie
@elie
If you’re struggling with anything that worked with page router then just add use client to the top of the file. Don’t wrestle with it.
1 reply
0 recast
0 reaction

one of the many matts pfp
one of the many matts
@1ofthemanymatts
for nprogress, put it in your app/layout and then hook the navigation events in next/navigation router within an effect
1 reply
0 recast
0 reaction

Brian Kim pfp
Brian Kim
@brianjckim
you can do something like this for the last one
1 reply
0 recast
0 reaction

Drew Fisher pfp
Drew Fisher
@drewf.eth
For #1, make everything a server component, split everything into components when there’s something new you’d be okay with streaming in, then use <Suspense> liberally with skeletons for each thing you’re waiting to be streamed.
0 reply
0 recast
0 reaction