Skip to content

Update transitions branch with upstream changes#53

Open
rauhryan wants to merge 57 commits into
transitionsfrom
rr/pr-27-upstream-merge-fixes
Open

Update transitions branch with upstream changes#53
rauhryan wants to merge 57 commits into
transitionsfrom
rr/pr-27-upstream-merge-fixes

Conversation

@rauhryan
Copy link
Copy Markdown
Collaborator

@rauhryan rauhryan commented May 31, 2026

Summary

This is a follow-up PR targeting the transitions branch from #27. It merges the latest main changes into the transitions work and includes small integration fixes found while validating the merged branch.

Changes

  • Merge latest origin/main into transitions
  • Resolve the upstream demo/ -> examples/keyboard/ relocation for transition demos
  • Export animating from the WASM build so the rebuilt native module matches term-native.ts
  • Include transition bytes when sizing snapshot() buffers
  • Allow transition ops in runtime validation
  • Enforce the existing spec rule that transition duration must be nonnegative

This branch is intended for Charles to merge into the PR #27 source branch (transitions).

cowboyd and others added 30 commits April 17, 2026 19:47
Introduces a new `snapshot(ops)` constructor that pre-packs a directive
array into its transfer encoding. The returned opaque `Op` can be
spliced into any directive array, and during packing its bytes are
copied directly into the command buffer without re-encoding.

This enables higher-level frameworks to implement dirty tracking:
unchanged component subtrees can reuse a cached snapshot, skipping
the per-frame packing cost entirely.
Co-Authored-By: ghostdevv <git@willow.sh>
for some reason the schema for the actions wants it to be an array
Without this it means that, for example, if I push a change to a PR then
shortly push again this workflow will be running twice. This change will
cancel the old run before starting the new one, which reduces the
overall actions cost and DX as you don't have extra runs
Without this it means that, for example, if I push a change to a PR then
shortly push again this workflow will be running twice. This change will
cancel the old run before starting the new one, which reduces the
overall actions cost and DX as you don't have extra runs
ghostdevv and others added 27 commits May 24, 2026 15:53
This should be using OIDC for publishing
Reverts three changes that need benchmarks before landing:
- -Oz / wasm-opt
- brotli+Z85 wasm compression
- wcwidth.c rewrite
chore: update preview workflow
chore: update verify workflow
Adds performance benchmarks with tinybench, benchmark CI via CodSpeed
chore: update publish workflow
Add snapshot() for pre-packing directive subtrees
# Conflicts:
#	examples/keyboard/clay-transitions.ts
#	examples/keyboard/transitions.ts
@pkg-pr-new
Copy link
Copy Markdown

pkg-pr-new Bot commented May 31, 2026

Open in StackBlitz

npm i https://pkg.pr.new/clayterm@53

commit: 7eab1e4

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.

5 participants