Fix client validation flickers

[freekh]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: 4a78351

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@valbuild/ui	Patch
@valbuild/server	Patch
@valbuild/next	Patch
@valbuild/react	Patch
@valbuild/cli	Patch

Not sure what this means? Click here to learn what changesets are.

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

[Copilot]

Pull request overview

This PR updates the Val UI sync engine to prevent a brief UI “flicker” in fs mode when publish() succeeds and the patch chain is dropped, by baking the currently optimistic (patched) value into serverSources before patch state is reset.

Changes:

• In ValSyncEngine.publish() (fs mode), bake the patched source value into serverSources before clearing patch state, then invalidate affected module sources.
• Add a regression test covering the fs-mode publish flicker, plus a fake /save implementation in the test harness to model fs behavior.
• Add a changeset for @valbuild/ui describing the flicker fix.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
packages/ui/spa/ValSyncEngine.ts	Bakes patched values into serverSources in fs mode during publish to avoid reverting to the unpatched base between patch deletion and next sources refresh.
packages/ui/spa/ValSyncEngine.test.ts	Adds a regression test for the publish flicker and extends the fake API with an fs-mode /save behavior.
examples/next/val.config.ts	Enables a hard-coded project in the example config (appears unrelated to the sync-engine flicker fix).
examples/next/app/blogs/[blog]/page.val.ts	Changes example blog title content (appears unrelated to the sync-engine flicker fix).
.changeset/fix-save-content-flicker.md	Documents the UI patch release for the flicker fix.

Comments suppressed due to low confidence (1)

packages/ui/spa/ValSyncEngine.ts:3143

• In fs mode publish() sets this.globalServerSidePatchIds = [], but it never calls invalidateGlobalServerSidePatchIds(). If getGlobalServerSidePatchIdsSnapshot() has been read previously, the cached snapshot (and any listeners) can remain stale even though the underlying IDs were cleared.

          // In fs mode we delete all patch ids, so we start fresh
          this.globalServerSidePatchIds = [];
          console.debug("Deleting all patch ids");
        }