Bump viv to 0.22.0 and deck.gl/luma.gl ecosystem to 9.3.5

[xinaesthete]

Summary

• viv 0.21.0 → 0.22.0: bumps @hms-dbmi/viv, @vivjs/views, and @vivjs/constants in the pnpm catalog
• deck.gl / luma.gl 9.2.x → 9.3.5: viv 0.22.0 requires @deck.gl/* at ~9.3.3; updated the entire deck.gl and luma.gl sub-package ecosystem in the catalog to avoid peer dependency conflicts (core, layers, geo-layers, extensions, widgets, react, mesh-layers, aggregation-layers, engine, constants, shadertools, gltf, webgl, loaders.gl/core)
• Fix broken import paths in packages/vis/scripts/dev.mjs: ../../scripts/ resolved to packages/scripts/ (wrong); corrected to ../../../scripts/ so it resolves to the repo root scripts/ directory. This was preventing pnpm dev from starting.

Reviewer notes

The deck.gl/luma.gl sub-packages (@deck.gl/widgets, @luma.gl/gltf, etc.) previously weren't listed in the catalog as they were pulled in transitively. They now have explicit catalog entries because bumping only @deck.gl/core and @luma.gl/core left the transitive sub-packages on 9.2.x, causing peer conflicts against the 9.3.x cores.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@xinaesthete, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 32 seconds

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: de7e9061-0a04-4c97-861d-07aaad863b36

📥 Commits

Reviewing files that changed from the base of the PR and between 113c6ae and 575ed19.

⛔ Files ignored due to path filters (1)

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (3)

• .changeset/bump-viv-0-22.md
• packages/vis/scripts/dev.mjs
• pnpm-workspace.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/great-archimedes-044566

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}