fix(deps): bump @opentui/core and @opentui/solid to 0.4.5 - #335
Open
fro-bot wants to merge 1 commit into
Open
Conversation
Refreshes the stale Renovate PR #135 (which targeted 0.4.3) to the current upstream release 0.4.5. Pins both packages to the same version via an `overrides` entry so TypeScript resolves branded renderable types from a single installation, preventing the duplicate-type-identity regressions that @opentui/solid@0.4.x introduces by bundling its own @opentui/core. Verified: bun run typecheck, build, test:unit (322 pass), test:tui (37 pass), node ESM export-shape smoke test, all clean.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refreshes the stale Renovate PR #135 (which targeted
0.4.3) to the current upstream release0.4.5. Brought forward as a fro-bot-managed branch so the0.4.xruntime upgrade can land cleanly with the@opentui/coreoverride +patchchangeset in place.@opentui/core0.2.7→0.4.5@opentui/solid0.2.7→0.4.5Why this exists
@opentui/solid@0.4.xbundles its own copy of@opentui/core, which produces duplicate type identities (TextRenderable,BoxRenderable,KeyEvent, …) that breakbun run typecheck. Pinning both packages to the same version via a newoverrides.@opentui/coreentry forces TypeScript to resolve branded renderable types from the single root installation. This mirrors the approach Renovate queued in PR #135; carrying it here against upstream latest (0.4.5) supersedes the stale Renovate branch.Verification
bun install✅ clean (5 packages added; only benignincorrect peer dependencywarnings:solid-js@1.9.14vs@opentui/solidpeer1.9.12).bun run typecheck✅ cleanbun run build✅ exit 0 (dist/populated)bun run test:unit✅ 322 pass / 0 fail / 1279 expect() callsbun run test:tui✅ 37 pass / 0 fail / 228 expect() calls (with benignEventTarget memory leakwarnings from OpenTUI internals)dist/index.jsexposes onlydefault/function)bun run lintemits the same pre-existingbiome.jsonschema2.5.5 vs 2.5.6info present onmain(cleared by PR chore(dev): bump biome config schema to 2.5.6 #332).Changeset
.changeset/opentui-core-solid-0.4.5.md→patch(only the runtime@opentui/*deps change onmain).Supersedes
PR #135 (
renovate/opentui-solid-0.x, stale0.4.3). Once this lands, PR #135 can be closed (Renovate will rebase it otherwise; recommend manual close + Renovate ignore comment to avoid reopening).Posted by Fro Bot Agent [bot] — non-interactive CI autoheal.