rm not tested pathfinder, detect issues

[zardoy]

Summary by CodeRabbit

• Chores

  • Removed an unused development dependency to streamline setup.
  • Expanded build-time compatibility checks to block unsupported modules and improved error messages with clearer origin context.

• Refactor

  • Cleaned up legacy pathfinding integration with no impact to public behavior or APIs.

• Tests

  • No changes.

• Documentation

  • No changes.

• Bug Fixes

  • No user-facing fixes in this release.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Removed mineflayer-pathfinder as a devDependency and stripped its usage from src/connect.ts. Updated build configuration to broaden NormalModuleReplacementPlugin matching and incompatibility checks to include prismarine-physics, with adjusted error logging.

Changes

Cohort / File(s)	Summary
Dependency cleanup package.json	Removed devDependency "mineflayer-pathfinder".
Build config adjustments renderer/rsbuildSharedConfig.ts	Broadened NormalModuleReplacementPlugin test to /data
Runtime code cleanup src/connect.ts	Deleted import of mineflayer-pathfinder and removal of window.pathfinder assignment; no other logic changes.

Sequence Diagram(s)

sequenceDiagram
  participant Build as Build (Rsbuild/Webpack)
  participant Plugin as NormalModuleReplacementPlugin
  participant Logger as Logger
  participant Process as Process

  Build->>Plugin: Resolve module request
  Plugin->>Plugin: Check request matches /data|prismarine-physics/
  alt Incompatibility detected (request contains minecraft-data/data/pc/1.* or prismarine-physics)
    Plugin->>Logger: Log error with issuer (from: <issuer>)
    Plugin->>Process: exit(1)
  else
    Plugin-->>Build: Proceed with existing remappings/handling
  end

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Suggested labels

Review effort 3/5

Poem

I nibbled the paths, now lighter we run,
Snipped a vine of code—clean under the sun.
The builder now watches new stones and sticks,
“Prismarine?” it squeaks—quick sanity checks.
Ears up, hops swift, fewer trails to mind—
Onward we scamper, sleek and refined. 🐇✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

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

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these settings in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between e2b141c and 4dbb128.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (3)

• package.json (0 hunks)
• renderer/rsbuildSharedConfig.ts (1 hunks)
• src/connect.ts (0 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch possible-minflayer-pnpm-issue

---

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

🪧 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.
  • 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.
• 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

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

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• 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.