Merge pull request #9068 from ever-co/fix/mcp-electron-build

[evereq]

[Fix] Fix build errors issues for MCP server electron desktop app

PR

• Have you followed the contributing guidelines?
• Have you explained what your changes do, and why they add value?

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

---

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch develop

---

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.
  • 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.
  • @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 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.
  • @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 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.

[greptile-apps]

Greptile Summary

This PR fixes build errors for the MCP (Model Context Protocol) server electron desktop app through configuration adjustments and build pipeline integration. The MCP server is a new component in the Ever Gauzy platform that enables desktop app functionality through the Model Context Protocol.

The changes address three key areas:

1. Package Configuration: The MCP server's package.json is updated to use main.js as the entry point instead of index.js, and the problematic @gauzy/config dependency is removed from both workspaces and dependencies to eliminate build conflicts.

2. Build Pipeline Integration: The root package.json is modified to include MCP server builds in the comprehensive build scripts (build:package:all, build:package:all:prod, build:package:all:docker) and adds a new Docker-specific build command. A minor spacing fix is also applied to prevent syntax errors.

3. TypeScript Configuration: The tsconfig.electron.json is restructured to properly inherit from the base configuration, removes conflicting electron type definitions, updates the module system to ES2022, and adjusts include paths to match the MCP server's unique entry point structure.

These changes follow established patterns in the codebase where desktop applications are configured with specific entry points and build configurations, while ensuring the MCP server integrates seamlessly with the overall build system.

PR Description Notes:

• The PR template checkboxes are not checked, which violates the contributing guidelines
• The description lacks explanation of what the changes do and why they add value

Confidence score: 3/5

• This PR appears to address legitimate build configuration issues but has some concerning aspects that require attention.
• The removal of @gauzy/config dependency could potentially break functionality if the main.js file still relies on configuration from that package, and there's insufficient context to verify this won't cause runtime issues.
• The following files need more attention: apps/server-mcp/src/package.json (due to dependency removal), apps/server-mcp/tsconfig.electron.json (configuration inheritance changes)

_{3 files reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}