perf: use hook filters

[TheAlexLichter]

Refactor the route handling logic to utilize a hook filter, improving performance and maintainability when using Rolldown as bundler.

This should be in line with what loadInclude/transformInclude does for webpack too.

Related issue

e18e/ecosystem-issues#171

Summary by CodeRabbit

Summary by CodeRabbit

• Refactor
  • Improved internal plugin structure for module filtering and handling, making the system more modular and maintainable. No changes to user-facing features or exported functionality.

[coderabbitai]

Walkthrough

The code refactors the plugin's internal logic to use structured filter objects with explicit include patterns and handler functions for module filtering, resolution, transformation, and loading. Constants are introduced for precomputed file paths and regex patterns, replacing repeated inline computations. The resolveId, transform, and load hooks are restructured into objects with declarative filters and handlers, but their core logic and external API remain unchanged. Additionally, a new exported function exactRegex was added to moduleConstants.ts to create exact-match regex patterns.

Changes

Files/Paths	Change Summary
src/index.ts	Refactored plugin hooks (resolveId, transform, load) to use filter/handler objects; introduced constants for precomputed file paths and regex; reorganized internal logic for clarity and modularity; no changes to exported API.
src/core/moduleConstants.ts	Added exported function exactRegex(input: string): RegExp to generate exact-match regexes; introduced internal helper escapeRegex; no changes to existing logic.

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/unplugin-vue-router@631

commit: 4c2d3eb

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 62.35%. Comparing base (3525b84) to head (4c2d3eb).
Report is 2 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #631   +/-   ##
=======================================
  Coverage   62.35%   62.35%           
=======================================
  Files          32       32           
  Lines        3140     3140           
  Branches      586      586           
=======================================
  Hits         1958     1958           
  Misses       1176     1176           
  Partials        6        6           

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

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

src/core/moduleConstants.ts (1)

39-47: Consider adding JSDoc comments to the new utility functions.

The implementation is correct, but adding JSDoc documentation would improve maintainability by explaining the purpose and parameters of these utility functions.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 39d1a81 and d6c8214.

📒 Files selected for processing (2)

• src/core/moduleConstants.ts (1 hunks)
• src/index.ts (5 hunks)

🚧 Files skipped from review as they are similar to previous changes (1)

• src/index.ts