-
Notifications
You must be signed in to change notification settings - Fork 36
fix: dep #313
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: dep #313
Conversation
WalkthroughThe changes refactor the definition and import of the Changes
Suggested reviewers
Poem
Warning There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure. 🔧 ESLint
plugin/controller/lib/impl/mcp/MCPControllerRegister.tsOops! Something went wrong! :( ESLint: 8.57.1 ESLint couldn't find the plugin "eslint-plugin-eggache". (The package "eslint-plugin-eggache" was not found when loaded as a Node module from the directory "".) It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
The plugin "eslint-plugin-eggache" was referenced from the config file in ".eslintrc » eslint-config-egg/typescript » ./index.js". If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team. plugin/mcp-proxy/types.tsOops! Something went wrong! :( ESLint: 8.57.1 ESLint couldn't find the plugin "eslint-plugin-eggache". (The package "eslint-plugin-eggache" was not found when loaded as a Node module from the directory "".) It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
The plugin "eslint-plugin-eggache" was referenced from the config file in ".eslintrc » eslint-config-egg/typescript » ./index.js". If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team. plugin/mcp-proxy/index.tsOops! Something went wrong! :( ESLint: 8.57.1 ESLint couldn't find the plugin "eslint-plugin-eggache". (The package "eslint-plugin-eggache" was not found when loaded as a Node module from the directory "".) It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:
The plugin "eslint-plugin-eggache" was referenced from the config file in ".eslintrc » eslint-config-egg/typescript » ./index.js". If you still can't figure out the problem, please stop by https://eslint.org/chat/help to chat with the team.
✨ Finishing Touches
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
d19fc07
to
5b599ef
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 0
🧹 Nitpick comments (1)
plugin/mcp-proxy/test/fixtures/apps/mcp-proxy/app/controller/app.ts (1)
12-12
: Prefer using the published package import forMCPProtocols
.
The deep relative path is brittle and does not reflect real-world consumption of the plugin. Importing directly from the package API makes fixtures clearer and more robust:- import { MCPProtocols } from '../../../../../../types'; + import { MCPProtocols } from '@eggjs/mcp-proxy/types';
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (6)
plugin/controller/lib/impl/mcp/MCPControllerRegister.ts
(1 hunks)plugin/mcp-proxy/index.ts
(1 hunks)plugin/mcp-proxy/package.json
(2 hunks)plugin/mcp-proxy/test/fixtures/apps/mcp-proxy/app/controller/app.ts
(1 hunks)plugin/mcp-proxy/types.ts
(1 hunks)plugin/mcp-proxy/typings/index.d.ts
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (8)
- GitHub Check: Runner-ubuntu (22)
- GitHub Check: Runner-ubuntu (18)
- GitHub Check: Runner-ubuntu (20)
- GitHub Check: Runner-ubuntu (16)
- GitHub Check: Runner-macos (18)
- GitHub Check: Runner-macos (16)
- GitHub Check: Analyze (javascript)
- GitHub Check: Analyze (typescript)
🔇 Additional comments (6)
plugin/mcp-proxy/package.json (2)
23-24
: Correctly include new type definition files in the published package.
Addingtypes.js
andtypes.d.ts
to thefiles
array ensures that the relocatedMCPProtocols
enum is bundled on npm.
59-59
: Verifyeventsource-parser
subpath import compatibility.
Ensure that version^3.0.1
exposes astream
entry point (eventsource-parser/stream
) as used in the codebase.plugin/mcp-proxy/typings/index.d.ts (1)
5-5
: Re-exportMCPProtocols
from the new types module.
Updating the export source to'../types'
aligns with the refactoring and ensures downstream TypeScript consumers see the correct enum.plugin/mcp-proxy/index.ts (1)
16-16
: ImportMCPProtocols
from the dedicated types file.
Switching to./types
keeps the runtime import in sync with where the enum is defined.plugin/controller/lib/impl/mcp/MCPControllerRegister.ts (1)
23-23
: Update import path forMCPProtocols
.
Importing from@eggjs/mcp-proxy/types
reflects the relocation of the enum and maintains type consistency.plugin/mcp-proxy/types.ts (1)
1-5
: Well-formed enum definition.
TheMCPProtocols
enum cleanly centralizes the protocol constants with matching string values. Naming is consistent, and the file structure aligns with the refactor.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Checklist
npm test
passesAffected core subsystem(s)
Description of change
Summary by CodeRabbit
New Features
Chores