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

feat(fs-router): page parts added #1318

Draft
wants to merge 4 commits into
base: page-part-component
Choose a base branch
from

Conversation

tylersayshi
Copy link
Member

to come after #1313

@tylersayshi tylersayshi self-assigned this Mar 24, 2025
Copy link

vercel bot commented Mar 24, 2025

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

Name Status Preview Updated (UTC)
waku ✅ Ready (Inspect) Visit Preview Mar 25, 2025 1:55am

Copy link

codesandbox-ci bot commented Mar 24, 2025

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

@tylersayshi tylersayshi changed the base branch from main to page-part-component March 24, 2025 03:41
createPagePart({
path,
component: mod.default,
render: 'static',
Copy link
Member

Choose a reason for hiding this comment

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

It feels like we should make "render: 'static'" by default for createPage.

Copy link
Member Author

Choose a reason for hiding this comment

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

So nextjs actually used this default and had a lot of user issues with it. Next 15 made pages dynamic by default (by popular demand): link to announcement

I should make the pagePart default render be dynamic. It matches what seems to be intuitive for users.

Maybe we should make layouts dynamic by default as well if we want consistency though?

Copy link
Member

Choose a reason for hiding this comment

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

Maybe we should make layouts dynamic by default as well if we want consistency though?

That sounds better for consistency.

Though, this is still a simple rule:

  • layout, root: static by default
  • page, page parts: dynamic by default

Hm, I may prefer everything dynamic or static by default. Let's discuss with @sandren after we finish v0.22.

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.

2 participants