chore: fix coderabbitai problem

[Bmongo]

Summary by CodeRabbit

• Chores
  • Updated internal configuration structure for ESLint.
  • Removed the "exbuild" development dependency.

[coderabbitai]

Walkthrough

The ESLint configuration export in eslint.config.js was refactored to use an array-based structure for defineConfig, without altering the actual configuration content. Additionally, the exbuild development dependency was removed from package.json.

Changes

Cohort / File(s)	Change Summary
ESLint Config Refactor eslint.config.js	Changed the export from defineConfig(...) to defineConfig([...]), switching to an array input for configuration.
Dependency Cleanup package.json	Removed the exbuild package from the devDependencies section.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

A hop and a skip through config and code,
The lint rules now nest in an arrayed abode.
Exbuild departs with a silent goodbye,
The package is lighter, the carrots run dry.
With a twitch of my nose and a reviewer's delight,
These changes are simple—approved at first sight! 🥕✨

Note

🔌 MCP (Model Context Protocol) integration is now available in Early Access!

Pro users can now connect to remote MCP servers under the Integrations page to get reviews and chat conversations that understand additional development context.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment

---

🪧 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.
  • Explain this complex logic.
  • 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 explain this code block.
• 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 explain its main purpose.
  • @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 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 generate unit tests to generate unit tests for 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.

[coderabbitai]

Actionable comments posted: 1

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 546394c and a42117b.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (2)

• eslint.config.js (1 hunks)
• package.json (0 hunks)

💤 Files with no reviewable changes (1)

• package.json

[coderabbitai]

⚠️ Potential issue

Spread array-based configs to avoid nested arrays in flat config

Several imported presets are arrays. Without spreading, defineConfig receives nested arrays and ESLint will fail at runtime. Spread array-based configs; keep object-based React configs as-is. Prettier should remain last.

-export default defineConfig([
-  tseslint.configs.recommended,
-  reactPlugin.configs.flat.recommended,
-  reactPlugin.configs.flat['jsx-runtime'],
-  eslintPluginPrettierRecommended,
-  eslintConfigPrettier,
-]);
+export default defineConfig([
+  ...tseslint.configs.recommended,
+  reactPlugin.configs.flat.recommended,
+  reactPlugin.configs.flat['jsx-runtime'],
+  ...eslintPluginPrettierRecommended,
+  ...eslintConfigPrettier,
+]);

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	export default defineConfig([
	tseslint.configs.recommended,
	reactPlugin.configs.flat.recommended,
	reactPlugin.configs.flat['jsx-runtime'],
	eslintPluginPrettierRecommended,
	eslintConfigPrettier
	);
	eslintConfigPrettier,
	]);
	export default defineConfig([
	...tseslint.configs.recommended,
	reactPlugin.configs.flat.recommended,
	reactPlugin.configs.flat['jsx-runtime'],
	...eslintPluginPrettierRecommended,
	...eslintConfigPrettier,
	]);

🤖 Prompt for AI Agents

In eslint.config.js around lines 7 to 13, the array-based ESLint configs are
passed as nested arrays to defineConfig, causing runtime failures. To fix this,
spread the array-based configs using the spread operator (...) so that
defineConfig receives a flat array. Keep object-based React configs unchanged
and ensure the Prettier config remains last in the array.