⚡ Bolt: [performance improvement] Optimize DOM queries by replacing querySelectorAll[0] with querySelector

[bartholomej]

💡 What:
Replaced several instances of el.querySelectorAll(selector)[0] with el.querySelector(selector) in search.helper.ts, creator.helper.ts, and user-ratings.helper.ts. Also added inline comments documenting the optimization.

🎯 Why:
When using node-html-parser, querySelectorAll forces the parser to traverse the entire DOM subtree to find all possible matches and allocate an array for them. When we only need the first element (using [0]), this is highly inefficient. querySelector halts traversal immediately upon finding the first match, saving CPU cycles and memory, especially on deeply nested HTML structures like CSFD.cz profiles.

📊 Impact:
Reduces unnecessary DOM traversals and memory allocations during array creation in search parsing, creator film extraction, and user rating parsing. This creates a measurable reduction in CPU overhead during multi-page fetching loops.

🔬 Measurement:
Run yarn test to verify that all parsing helpers correctly extract the identical DOM values as before (due to querySelector mimicking the document order match of querySelectorAll()[0]). No functional regressions exist.

---

PR created automatically by Jules for task 17101398890926285675 started by @bartholomej

Summary by CodeRabbit

• Refactor
  • Enhanced performance of internal data retrieval operations by optimizing element selection patterns across creator information, search, and user rating data handlers. These improvements simplify code and boost performance while maintaining complete functional equivalence with no user-facing changes.

[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]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 599cd1a1-f12f-4968-8570-5939cfb1ca10

📥 Commits

Reviewing files that changed from the base of the PR and between 0e50ef5 and 4c9de39.

📒 Files selected for processing (3)

• src/helpers/creator.helper.ts
• src/helpers/search.helper.ts
• src/helpers/user-ratings.helper.ts

---

📝 Walkthrough

Walkthrough

Three helper files updated to use querySelector() instead of querySelectorAll(...)[0], simplifying DOM element selection patterns. No behavioral changes to public APIs; all functions retain identical return types and error handling.

Changes

Cohort / File(s)	Summary
DOM Selector Refactoring src/helpers/creator.helper.ts, src/helpers/search.helper.ts, src/helpers/user-ratings.helper.ts	Replaced querySelectorAll(...)[0] patterns with querySelector(...) across three helper functions. Maintains functional equivalence while simplifying selector logic.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• ESM + CommonJS build 🎉  #18: Modifies the same three helper functions and DOM selector patterns (getCreatorFilms, getSearchYear, getUserRatingYear).

Suggested labels

enhancement

Poem

🐰 A rabbit hops through DOM today,
With selectors cleaner than yesterday,
One query instead of searching all,
No [0] indexing—we've answered the call!
Simpler, swifter, the code now sings,
Refactoring brings such nimble things! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	❓ Inconclusive	The PR description comprehensively covers the what, why, and impact. However, the required template sections (Type of change, Related Issues, Checklist) are not filled out.	Complete the template by selecting the appropriate change type, linking any related issues, and checking off verification steps performed.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely summarizes the main change: replacing querySelectorAll[0] with querySelector for DOM query optimization.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch bolt/optimize-dom-query-selectors-17101398890926285675

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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.}

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.47%. Comparing base (0e50ef5) to head (4c9de39).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #116   +/-   ##
=======================================
  Coverage   99.47%   99.47%           
=======================================
  Files          34       34           
  Lines         766      766           
  Branches      192      192           
=======================================
  Hits          762      762           
  Misses          4        4           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.