Skip to content

feat: enables client-side navigation in Makeswift builder#2913

Draft
agurtovoy wants to merge 1 commit intointegrations/makeswiftfrom
aleksey/makeswift-builder-client-side-navigation
Draft

feat: enables client-side navigation in Makeswift builder#2913
agurtovoy wants to merge 1 commit intointegrations/makeswiftfrom
aleksey/makeswift-builder-client-side-navigation

Conversation

@agurtovoy
Copy link
Contributor

What/Why?

Enables client-side navigation in Makeswift builder by upgrading Catalyst to the latest Makeswift runtime.

Testing

Migration

@vercel
Copy link

vercel bot commented Mar 9, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
catalyst Ready Ready Preview, Comment Mar 9, 2026 5:06pm

Request Review

@changeset-bot
Copy link

changeset-bot bot commented Mar 9, 2026

⚠️ No Changeset found

Latest commit: 22c8123

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

"@conform-to/zod": "^1.6.1",
"@icons-pack/react-simple-icons": "^11.2.0",
"@makeswift/runtime": "^0.26.0",
"@makeswift/runtime": "https://pkg.pr.new/makeswift/makeswift/@makeswift/runtime@1259",
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This needs to be changed to a released runtime version before we can merge this PR.

Copy link
Contributor

Choose a reason for hiding this comment

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

I also think we need Next 16 + React 19 in order to merge a new runtime version as well. @matthewvolk is tackling this right now.

Copy link
Member

Choose a reason for hiding this comment

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

The new runtime version should still work with Next 15 + React 18. The runtime uses Suspense instead of Activity when it's on React 18.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@chanceaclark Just to clarify, we don't have to upgrade to Next 16 + React 19 at the same time; Makeswift runtime still supports React 18 and older Next.js versions all the way down to 13.4, so we can tackle the Next 16/React 19 upgrade to get the <Activity> performance improvements independently of upgrading Makeswift runtime to pull in other features/bug fixes.

Copy link
Contributor

Choose a reason for hiding this comment

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

Interesting 🤔 I've been going with the assumption that it's hand-in-hand, specifically to fix that performance issue with <Activity />. TIL that we should be good then.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, we need runtime@0.26.3+, Next 16, and React 19 to get the <Activity /> performance improvements, but otherwise, these are not coupled. If we want to, we can upgrade to runtime@0.26.3 right now without forcing the Next 16 / React 19 upgrade.

Enabled by upgrading to the latest Makeswift runtime
@agurtovoy agurtovoy force-pushed the aleksey/makeswift-builder-client-side-navigation branch from 4f1d31a to 22c8123 Compare March 9, 2026 17:03
Copy link
Contributor

@jorgemoya jorgemoya left a comment

Choose a reason for hiding this comment

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

Should we include a changeset?

@jorgemoya
Copy link
Contributor

jorgemoya commented Mar 9, 2026

Tagging with do not merge until we have that released runtime version.

Edit: nevermind, it's a draft PR 🤦

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