⚡ Bolt: optimize MatrixTechnique rendering performance

[darksheer]

💡 What: Refactored MatrixTechnique.vue to move the matrix-data.json import and technique Map initialization to the module scope (outside the Vue component definition) and changed the computed technique property to use an O(1) map lookup instead of O(N) array filtering.

🎯 Why:

1. Vue's reactivity system automatically wraps all objects defined inside data() with proxies. For a massive static dataset like matrix-data.json (~1600 lines) which never mutates, this introduced massive initialization overhead for every MatrixTechnique instance rendered.
2. Looking up a single technique ID against a large array using .filter() is O(N). The matrix renders many techniques simultaneously, compounding the cost.

📊 Impact: Removes immense hidden reactivity overhead by keeping the static dataset out of Vue's observation system. Radically speeds up component evaluation by turning O(N) linear array scans into O(1) Map lookups.

🔬 Measurement: Verify by running npm run dev and observing rendering performance on the home page matrix, or running npm run type-check and npm run build to confirm typings remain secure.

---

PR created automatically by Jules for task 14046808348584330355 started by @darksheer

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[coderabbitai]

Warning

Review limit reached

@darksheer, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 40 minutes and 28 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 667fbe7c-ff7c-4ac5-ae3c-9d81816a0668

📥 Commits

Reviewing files that changed from the base of the PR and between 65e835b and cc70168.

📒 Files selected for processing (2)

• .jules/bolt.md
• research/f3-snapshot-1835d4f/src/components/MatrixTechnique.vue

---

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 and usage tips.}