Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Waku router under the hood and add guides to website #1311

Merged
merged 7 commits into from
Mar 20, 2025
Merged

Conversation

tylersayshi
Copy link
Member

This is an idea for a router post. I am happy to reword, restructure or whatever.

It was helpful for me to organize my thoughts to look a bit closer at what is loaded when on each route, so I think a post to talk through some of this has some value.

Excited to hear what y'all think :)

This is an idea for a router post. I am happy to reword, restructure
or whatever.

It was helpful for me to organize my thoughts to look a bit
closer at what is loaded when on each route, so I think a
post to talk through some of this has some value.

Excited to hear what y'all think :)
Copy link

vercel bot commented Mar 17, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment
Name Status Preview Updated (UTC)
waku ⬜️ Ignored (Inspect) Visit Preview Mar 20, 2025 7:07am

@tylersayshi tylersayshi changed the title docs: Waku router under the hood docs: Waku router under the hood and add guides to website Mar 18, 2025
@tylersayshi tylersayshi marked this pull request as ready for review March 19, 2025 04:59
Copy link
Member

@dai-shi dai-shi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merging this for now. I think there should be room for improvement for website, like ordering guides, and styling.

@dai-shi dai-shi merged commit 7d11341 into main Mar 20, 2025
45 of 46 checks passed
@dai-shi dai-shi deleted the blog-router branch March 20, 2025 12:00
@rmarscher
Copy link
Collaborator

Maybe we should mention that Suspense and promises passed from the server can be used in layouts or pages to be able to display content while the rest is still being streamed down from the server. We could link out to the React docs about Suspense for people to learn more about it - https://react.dev/reference/react/Suspense

By default, a useTransition hook is used when navigating with the component. That causes the stale content inside Suspense to continue to display until the new content has loaded. There's an experimental unstable_startTransition to supply a different function to call. This can be the startTransition from your own useTransition hook call which can give you access to the isPending state. Or it's possible to pass a no-op function to skip useTransition entirely.

@dai-shi
Copy link
Member

dai-shi commented Mar 20, 2025

By default, a useTransition hook is used when navigating with the component.

That's no longer the case. #1257

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants