fix(cli): read actual composition dimensions in info and fix semver update check

[miguel-heygen]

Summary

• info command now reads actual data-width/data-height from the root composition element instead of hardcoding 1920x1080 or 1080x1920 based on a parser heuristic that defaults to "portrait"
• Update check now uses proper semver comparison instead of string inequality (!== VERSION). Previously reported "update available" when installed 0.2.1 and npm had 0.2.0

Part 2 of 5 in a stacked PR series fixing E2E test findings.

Test plan

• npx hyperframes info on a 1920x1080 project shows "1920x1080" (not "1080x1920")
• npx hyperframes info --json returns correct width/height fields
• Version check no longer reports downgrade as available update

[miguel-heygen]

• feat(engine): add experimental canvas renderer using drawElementImage API #198
• fix(templates): resolve all lint errors and warnings in bundled templates #197
• feat(fonts): add Playfair Display, Noto Sans JP, Roboto, and 4 more to deterministic font database #196
• fix(engine): suppress font-loading 404 noise in render console output #195
• fix(cli): read actual composition dimensions in info and fix semver update check #194 👈 (View in Graphite)
• feat(lint): add rules for non-deterministic code, missing clip class, overlapping tracks, and rAF detection #193
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[vanceingalls]

Review feedback

Important: Non-null assertions
packages/cli/src/commands/info.ts uses widthMatch[1]! and heightMatch[1]!. Same project convention issue as #193 — use widthMatch?.[1] ?? "" or a guard.

Note: No tests
Neither the semver comparison nor the dimension extraction have tests. Even one test for isNewerSemver("0.2.1", "0.2.0") === true would add confidence. The semver fix itself is clearly correct though.

Note: Regex brittleness
The dual-regex for data-width extraction works for all realistic compositions but is fragile. Ideally dimensions should come from the parser output rather than a separate regex pass.

[miguel-heygen]

Addressed:

1. Non-null assertions: Replaced widthMatch[1]! and heightMatch[1]! with widthMatch?.[1] optional chaining.

2. No tests: Fair point. The semver comparison is now delegated to compare-versions (a well-tested library), so we get their test coverage. For the regex dimension extraction, I agree a test would help but kept the scope focused on the fix for now.

3. Regex brittleness: Agreed long-term. The parser should expose actual data-width/data-height from the root composition element. Filed as a follow-up.

[vanceingalls]

Merge activity

• Apr 2, 9:12 PM UTC: @vanceingalls merged this pull request with Graphite.