Conversation
📝 WalkthroughWalkthroughMonorepo version bump from 3.73.0 to 3.74.0 across all core packages, plugins, and configuration. All Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~5 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request performs a comprehensive version bump from 3.73.0 to 3.74.0 across the entire monorepo, updating lerna.json and numerous package.json files. The changes include updating the package versions themselves as well as their internal @eggjs/* dependencies. Feedback was provided suggesting the use of exact version numbers for internal dependencies instead of caret ranges to ensure better consistency across the workspace.
core/tegg/package.json
Outdated
| "@eggjs/agent-runtime": "^3.74.0", | ||
| "@eggjs/ajv-decorator": "^3.74.0", | ||
| "@eggjs/aop-decorator": "^3.74.0", | ||
| "@eggjs/controller-decorator": "^3.74.0", | ||
| "@eggjs/core-decorator": "^3.74.0", | ||
| "@eggjs/dal-decorator": "^3.74.0", | ||
| "@eggjs/eventbus-decorator": "^3.74.0", | ||
| "@eggjs/standalone-decorator": "^3.74.0", | ||
| "@eggjs/tegg-background-task": "^3.74.0", | ||
| "@eggjs/tegg-common-util": "^3.74.0", | ||
| "@eggjs/tegg-dynamic-inject": "^3.74.0", | ||
| "@eggjs/tegg-lifecycle": "^3.74.0", | ||
| "@eggjs/tegg-loader": "^3.74.0", | ||
| "@eggjs/tegg-metadata": "^3.74.0", | ||
| "@eggjs/tegg-orm-decorator": "^3.74.0", | ||
| "@eggjs/tegg-runtime": "^3.74.0", | ||
| "@eggjs/tegg-schedule-decorator": "^3.74.0", | ||
| "@eggjs/tegg-transaction-decorator": "^3.74.0", | ||
| "@eggjs/tegg-types": "^3.74.0" |
There was a problem hiding this comment.
For internal dependencies within this monorepo, it's a good practice to use exact version numbers instead of caret ^ ranges. This ensures that all packages consistently use the same version, which helps prevent potential integration issues. This should be applied to all internal @eggjs/* dependencies across all package.json files in this PR.
| "@eggjs/agent-runtime": "^3.74.0", | |
| "@eggjs/ajv-decorator": "^3.74.0", | |
| "@eggjs/aop-decorator": "^3.74.0", | |
| "@eggjs/controller-decorator": "^3.74.0", | |
| "@eggjs/core-decorator": "^3.74.0", | |
| "@eggjs/dal-decorator": "^3.74.0", | |
| "@eggjs/eventbus-decorator": "^3.74.0", | |
| "@eggjs/standalone-decorator": "^3.74.0", | |
| "@eggjs/tegg-background-task": "^3.74.0", | |
| "@eggjs/tegg-common-util": "^3.74.0", | |
| "@eggjs/tegg-dynamic-inject": "^3.74.0", | |
| "@eggjs/tegg-lifecycle": "^3.74.0", | |
| "@eggjs/tegg-loader": "^3.74.0", | |
| "@eggjs/tegg-metadata": "^3.74.0", | |
| "@eggjs/tegg-orm-decorator": "^3.74.0", | |
| "@eggjs/tegg-runtime": "^3.74.0", | |
| "@eggjs/tegg-schedule-decorator": "^3.74.0", | |
| "@eggjs/tegg-transaction-decorator": "^3.74.0", | |
| "@eggjs/tegg-types": "^3.74.0" | |
| "@eggjs/agent-runtime": "3.74.0", | |
| "@eggjs/ajv-decorator": "3.74.0", | |
| "@eggjs/aop-decorator": "3.74.0", | |
| "@eggjs/controller-decorator": "3.74.0", | |
| "@eggjs/core-decorator": "3.74.0", | |
| "@eggjs/dal-decorator": "3.74.0", | |
| "@eggjs/eventbus-decorator": "3.74.0", | |
| "@eggjs/standalone-decorator": "3.74.0", | |
| "@eggjs/tegg-background-task": "3.74.0", | |
| "@eggjs/tegg-common-util": "3.74.0", | |
| "@eggjs/tegg-dynamic-inject": "3.74.0", | |
| "@eggjs/tegg-lifecycle": "3.74.0", | |
| "@eggjs/tegg-loader": "3.74.0", | |
| "@eggjs/tegg-metadata": "3.74.0", | |
| "@eggjs/tegg-orm-decorator": "3.74.0", | |
| "@eggjs/tegg-runtime": "3.74.0", | |
| "@eggjs/tegg-schedule-decorator": "3.74.0", | |
| "@eggjs/tegg-transaction-decorator": "3.74.0", | |
| "@eggjs/tegg-types": "3.74.0" |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (9)
core/mcp-client/package.json (1)
33-33:⚠️ Potential issue | 🟡 MinorFix repository directory field.
The
repository.directoryfield points to"core/langchain-decorator"but this package is located incore/mcp-client. This metadata inconsistency could affect repository tools and documentation.Note: This appears to be a pre-existing issue, not introduced by this PR.
📝 Proposed fix
- "directory": "core/langchain-decorator" + "directory": "core/mcp-client"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@core/mcp-client/package.json` at line 33, The package.json has an incorrect repository.directory value; update the "repository.directory" field in core/mcp-client's package.json (the repository.directory property) to "core/mcp-client" so the package metadata correctly points to this package's folder.core/ajv-decorator/package.json (1)
38-41:⚠️ Potential issue | 🟠 MajorRequired decorator dependencies are missing from this manifest.
This decorator package should include both
@eggjs/core-decoratorand@eggjs/tegg-typesindependencies.As per coding guidelines, "Decorator package `package.json` must include dependencies on `@eggjs/core-decorator` and `@eggjs/tegg-types`".Suggested dependency additions
"dependencies": { + "@eggjs/core-decorator": "^3.74.0", + "@eggjs/tegg-types": "^3.74.0", "@sinclair/typebox": "^0.32.20", "ajv": "^8.12.0" },🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@core/ajv-decorator/package.json` around lines 38 - 41, The package.json for the decorator is missing required runtime dependencies; update the "dependencies" object in core/ajv-decorator/package.json to include entries for "@eggjs/core-decorator" and "@eggjs/tegg-types" (add them alongside "@sinclair/typebox" and "ajv") so the decorator package declares and installs those required modules.plugin/common/package.json (1)
1-49:⚠️ Potential issue | 🟠 MajorMissing required
eggPluginandeggModulemetadata in plugin manifest.This package manifest is missing required plugin fields (
eggPlugin.name,eggPlugin.dependencies,eggModule.name), which breaks repository packaging conventions for plugin/standalone support.As per coding guidelines, "Plugin `package.json` files must include `eggPlugin` field with `name` and `dependencies` properties, and `eggModule` field with `name` property for standalone mode support".Suggested manifest shape
{ "name": "@eggjs/egg-module-common", "version": "3.74.0", + "eggPlugin": { + "name": "common", + "dependencies": [] + }, + "eggModule": { + "name": "common" + }, ... }🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugin/common/package.json` around lines 1 - 49, The package.json is missing the required plugin manifest metadata; add an "eggPlugin" object with at least "name" (e.g., the package short name) and "dependencies" (map of plugin dependencies or empty object) and add an "eggModule" object with a "name" property to support standalone mode; update the manifest in plugin/common/package.json to include these fields (eggPlugin.name, eggPlugin.dependencies, eggModule.name) so packaging and plugin loading conform to repository conventions.plugin/controller/package.json (1)
3-10:⚠️ Potential issue | 🟠 MajorAdd missing
eggModulemetadata for plugin standalone support.This manifest defines
eggPluginbut omitseggModule.name, which is required for plugin standalone mode/module scanning.As per coding guidelines: "Plugin `package.json` files must include `eggPlugin` field with `name` and `dependencies` properties, and `eggModule` field with `name` property for standalone mode support".Proposed fix
"eggPlugin": { "name": "teggController", "strict": false, "dependencies": [ "tegg" ] }, + "eggModule": { + "name": "teggController" + }, "version": "3.74.0",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugin/controller/package.json` around lines 3 - 10, The package.json defines an eggPlugin but lacks the required eggModule metadata for standalone/module scanning; add an "eggModule" object with a "name" property (matching the plugin name, e.g., the value in "eggPlugin.name" like "teggController") alongside the existing "eggPlugin" block so the manifest includes both "eggPlugin" (name, dependencies) and "eggModule" (name) entries to enable plugin standalone mode.plugin/eventbus/package.json (1)
1-10:⚠️ Potential issue | 🟠 Major
eggModuleis missing in this plugin package.Please add
eggModule.nameso this plugin is discoverable in standalone/module-scanning flows.🔧 Proposed fix
"eggPlugin": { "name": "eventbusModule", "strict": false, "dependencies": [ "tegg" ] }, + "eggModule": { + "name": "eventbusModule" + }, "description": "tegg event plugin",As per coding guidelines, "Plugin
package.jsonfiles must includeeggPluginfield withnameanddependenciesproperties, andeggModulefield withnameproperty for standalone mode support".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugin/eventbus/package.json` around lines 1 - 10, The package.json is missing the eggModule entry required for standalone/module-scanning; update the package.json to add an "eggModule" object with a "name" property (e.g. matching the plugin/module name like "eventbusModule" or "@eggjs/tegg-eventbus-plugin") alongside the existing "eggPlugin" field so the plugin is discoverable in standalone flows; ensure the new "eggModule.name" is a string and consistent with the "eggPlugin.name" if applicable.plugin/orm/package.json (1)
1-9:⚠️ Potential issue | 🟠 MajorMissing
eggModuledeclaration in plugin manifest.Please add an
eggModule.nameentry; without it, standalone mode/module scanning support is incomplete.🔧 Proposed fix
"eggPlugin": { "name": "teggOrm", "dependencies": [ "tegg" ] }, + "eggModule": { + "name": "teggOrm" + }, "version": "3.74.0",As per coding guidelines, "Plugin
package.jsonfiles must includeeggPluginfield withnameanddependenciesproperties, andeggModulefield withnameproperty for standalone mode support".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugin/orm/package.json` around lines 1 - 9, The package.json is missing the required eggModule declaration; update the manifest to add an eggModule object with a name property (matching the plugin/module identifier) so standalone mode/module scanning works; specifically modify the package.json to include an "eggModule": { "name": "teggOrm" } entry alongside the existing "eggPlugin" block to satisfy the plugin manifest rules.plugin/schedule/package.json (1)
1-10:⚠️ Potential issue | 🟠 MajorAdd missing
eggModulemetadata for standalone mode support.This plugin package still lacks
"eggModule": { "name": ... }, which is required for plugin standalone/module scanning support.🔧 Proposed fix
"eggPlugin": { "name": "teggSchedule", "dependencies": [ "tegg", "schedule" ] }, + "eggModule": { + "name": "teggSchedule" + }, "version": "3.74.0",As per coding guidelines, "Plugin
package.jsonfiles must includeeggPluginfield withnameanddependenciesproperties, andeggModulefield withnameproperty for standalone mode support".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugin/schedule/package.json` around lines 1 - 10, The package.json for `@eggjs/tegg-schedule-plugin` is missing the required eggModule metadata needed for standalone/module scanning; update the JSON to add an "eggModule" object with a "name" property (matching the module identity) alongside the existing "eggPlugin" field so that standalone mode can detect the module; ensure the new "eggModule": { "name": "tegg-schedule-plugin" } (or the appropriate canonical name) is present and valid JSON and does not conflict with the existing "eggPlugin" properties.plugin/aop/package.json (1)
3-9:⚠️ Potential issue | 🟠 MajorMissing
eggModuledeclaration in plugin manifest.Line 3 updates release metadata, but this plugin manifest still lacks the required
eggModule: { "name": ... }field for standalone mode support.Proposed fix
{ "name": "@eggjs/tegg-aop-plugin", "version": "3.74.0", "eggPlugin": { "name": "aopModule", "dependencies": [ "tegg" ] }, + "eggModule": { + "name": "aopModule" + }, "types": "typings/index.d.ts",As per coding guidelines:
plugin/*/package.jsonfiles must includeeggPluginandeggModulewith anameproperty for standalone mode support.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugin/aop/package.json` around lines 3 - 9, Add the required eggModule declaration to this plugin's package.json: the manifest currently has eggPlugin but is missing eggModule with a name property; update the package.json to include an "eggModule": { "name": "aopModule" } (or the appropriate module name) alongside the existing "eggPlugin" entry so both eggPlugin and eggModule with a name are present for standalone mode support.plugin/tegg/package.json (1)
1-9:⚠️ Potential issue | 🟠 Major
eggModuleis required but missing in this plugin package manifest.Line 9 bumps version, but the plugin still does not declare
eggModulewith aname, which is required for standalone mode compatibility.Proposed fix
{ "name": "@eggjs/tegg-plugin", "eggPlugin": { "name": "tegg", "dependencies": [ "teggConfig" ] }, + "eggModule": { + "name": "tegg" + }, "version": "3.74.0",As per coding guidelines:
plugin/*/package.jsonfiles must includeeggPluginfields and aneggModulefield withnamefor standalone mode support.🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@plugin/tegg/package.json` around lines 1 - 9, The package manifest is missing the required eggModule entry; update the plugin/tegg package.json to include an "eggModule" object with a "name" property (e.g. matching the module name) alongside the existing "eggPlugin" object so standalone mode works; ensure the new "eggModule": { "name": "tegg" } (or appropriate module name) is added and kept in sync with the package "name"/"eggPlugin.name" when you bump the "version".
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@core/standalone-decorator/package.json`:
- Around line 38-41: The package.json for the standalone-decorator is missing
required core dependencies; update the "dependencies" object to include
"@eggjs/core-decorator" and "@eggjs/tegg-types" (add exact package names to the
dependencies section alongside "@eggjs/tegg-common-util" and "reflect-metadata")
so the decorator package declares and installs the required core decorator types
and runtime; ensure versions follow your guideline (use semantic versions
consistent with the project) and run npm/yarn install to validate.
In `@plugin/config/package.json`:
- Around line 3-5: The package.json's eggPlugin entry is missing the required
"dependencies" property and the file lacks an "eggModule" field; update the
package.json to add eggPlugin.dependencies (an array of plugin names or an empty
array if none) alongside the existing eggPlugin.name ("teggConfig"), and add an
eggModule object with a "name" property matching the module (e.g., "teggConfig")
to support standalone module scanning.
In `@plugin/mcp-proxy/package.json`:
- Around line 4-6: Update the package.json's eggPlugin metadata to include a
dependencies property and add an eggModule entry for standalone mode: inside the
existing "eggPlugin" object (currently containing "name": "mcpProxy") add a
"dependencies" property (an object listing any plugin deps or an empty object if
none), and add a top-level "eggModule" object with a "name" property (typically
the package/plugin name, e.g., "mcpProxy"); ensure the property names are
spelled exactly as eggPlugin.dependencies and eggModule.name.
---
Outside diff comments:
In `@core/ajv-decorator/package.json`:
- Around line 38-41: The package.json for the decorator is missing required
runtime dependencies; update the "dependencies" object in
core/ajv-decorator/package.json to include entries for "@eggjs/core-decorator"
and "@eggjs/tegg-types" (add them alongside "@sinclair/typebox" and "ajv") so
the decorator package declares and installs those required modules.
In `@core/mcp-client/package.json`:
- Line 33: The package.json has an incorrect repository.directory value; update
the "repository.directory" field in core/mcp-client's package.json (the
repository.directory property) to "core/mcp-client" so the package metadata
correctly points to this package's folder.
In `@plugin/aop/package.json`:
- Around line 3-9: Add the required eggModule declaration to this plugin's
package.json: the manifest currently has eggPlugin but is missing eggModule with
a name property; update the package.json to include an "eggModule": { "name":
"aopModule" } (or the appropriate module name) alongside the existing
"eggPlugin" entry so both eggPlugin and eggModule with a name are present for
standalone mode support.
In `@plugin/common/package.json`:
- Around line 1-49: The package.json is missing the required plugin manifest
metadata; add an "eggPlugin" object with at least "name" (e.g., the package
short name) and "dependencies" (map of plugin dependencies or empty object) and
add an "eggModule" object with a "name" property to support standalone mode;
update the manifest in plugin/common/package.json to include these fields
(eggPlugin.name, eggPlugin.dependencies, eggModule.name) so packaging and plugin
loading conform to repository conventions.
In `@plugin/controller/package.json`:
- Around line 3-10: The package.json defines an eggPlugin but lacks the required
eggModule metadata for standalone/module scanning; add an "eggModule" object
with a "name" property (matching the plugin name, e.g., the value in
"eggPlugin.name" like "teggController") alongside the existing "eggPlugin" block
so the manifest includes both "eggPlugin" (name, dependencies) and "eggModule"
(name) entries to enable plugin standalone mode.
In `@plugin/eventbus/package.json`:
- Around line 1-10: The package.json is missing the eggModule entry required for
standalone/module-scanning; update the package.json to add an "eggModule" object
with a "name" property (e.g. matching the plugin/module name like
"eventbusModule" or "@eggjs/tegg-eventbus-plugin") alongside the existing
"eggPlugin" field so the plugin is discoverable in standalone flows; ensure the
new "eggModule.name" is a string and consistent with the "eggPlugin.name" if
applicable.
In `@plugin/orm/package.json`:
- Around line 1-9: The package.json is missing the required eggModule
declaration; update the manifest to add an eggModule object with a name property
(matching the plugin/module identifier) so standalone mode/module scanning
works; specifically modify the package.json to include an "eggModule": { "name":
"teggOrm" } entry alongside the existing "eggPlugin" block to satisfy the plugin
manifest rules.
In `@plugin/schedule/package.json`:
- Around line 1-10: The package.json for `@eggjs/tegg-schedule-plugin` is missing
the required eggModule metadata needed for standalone/module scanning; update
the JSON to add an "eggModule" object with a "name" property (matching the
module identity) alongside the existing "eggPlugin" field so that standalone
mode can detect the module; ensure the new "eggModule": { "name":
"tegg-schedule-plugin" } (or the appropriate canonical name) is present and
valid JSON and does not conflict with the existing "eggPlugin" properties.
In `@plugin/tegg/package.json`:
- Around line 1-9: The package manifest is missing the required eggModule entry;
update the plugin/tegg package.json to include an "eggModule" object with a
"name" property (e.g. matching the module name) alongside the existing
"eggPlugin" object so standalone mode works; ensure the new "eggModule": {
"name": "tegg" } (or appropriate module name) is added and kept in sync with the
package "name"/"eggPlugin.name" when you bump the "version".
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: fbebe551-a07b-4f59-83f2-c0543de7fd5f
📒 Files selected for processing (45)
core/agent-runtime/package.jsoncore/agent-tracing/package.jsoncore/ajv-decorator/package.jsoncore/aop-decorator/package.jsoncore/aop-runtime/package.jsoncore/background-task/package.jsoncore/common-util/package.jsoncore/controller-decorator/package.jsoncore/core-decorator/package.jsoncore/dal-decorator/package.jsoncore/dal-runtime/package.jsoncore/dynamic-inject-runtime/package.jsoncore/dynamic-inject/package.jsoncore/eventbus-decorator/package.jsoncore/eventbus-runtime/package.jsoncore/langchain-decorator/package.jsoncore/lifecycle/package.jsoncore/loader/package.jsoncore/mcp-client/package.jsoncore/metadata/package.jsoncore/orm-decorator/package.jsoncore/runtime/package.jsoncore/schedule-decorator/package.jsoncore/standalone-decorator/package.jsoncore/tegg/package.jsoncore/test-util/package.jsoncore/transaction-decorator/package.jsoncore/types/package.jsoncore/vitest/package.jsonlerna.jsonplugin/ajv/package.jsonplugin/aop/package.jsonplugin/common/package.jsonplugin/config/package.jsonplugin/controller/package.jsonplugin/dal/package.jsonplugin/dns-cache/package.jsonplugin/eventbus/package.jsonplugin/langchain/package.jsonplugin/mcp-client/package.jsonplugin/mcp-proxy/package.jsonplugin/orm/package.jsonplugin/schedule/package.jsonplugin/tegg/package.jsonstandalone/standalone/package.json
| "dependencies": { | ||
| "@eggjs/tegg-common-util": "^3.73.0", | ||
| "@eggjs/tegg-common-util": "^3.74.0", | ||
| "reflect-metadata": "^0.1.13" | ||
| }, |
There was a problem hiding this comment.
Decorator package is missing required core dependencies.
@eggjs/core-decorator and @eggjs/tegg-types should be present in dependencies for this decorator package.
Suggested dependency additions
"dependencies": {
+ "@eggjs/core-decorator": "^3.74.0",
"@eggjs/tegg-common-util": "^3.74.0",
+ "@eggjs/tegg-types": "^3.74.0",
"reflect-metadata": "^0.1.13"
},📝 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.
| "dependencies": { | |
| "@eggjs/tegg-common-util": "^3.73.0", | |
| "@eggjs/tegg-common-util": "^3.74.0", | |
| "reflect-metadata": "^0.1.13" | |
| }, | |
| "dependencies": { | |
| "@eggjs/core-decorator": "^3.74.0", | |
| "@eggjs/tegg-common-util": "^3.74.0", | |
| "@eggjs/tegg-types": "^3.74.0", | |
| "reflect-metadata": "^0.1.13" | |
| }, |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@core/standalone-decorator/package.json` around lines 38 - 41, The
package.json for the standalone-decorator is missing required core dependencies;
update the "dependencies" object to include "@eggjs/core-decorator" and
"@eggjs/tegg-types" (add exact package names to the dependencies section
alongside "@eggjs/tegg-common-util" and "reflect-metadata") so the decorator
package declares and installs the required core decorator types and runtime;
ensure versions follow your guideline (use semantic versions consistent with the
project) and run npm/yarn install to validate.
| "eggPlugin": { | ||
| "name": "teggConfig" | ||
| }, |
There was a problem hiding this comment.
Missing required dependencies property in eggPlugin field and missing eggModule field.
The eggPlugin field is missing the required dependencies property, and the package.json lacks an eggModule field entirely. As per coding guidelines, plugin package.json files must include:
eggPluginfield with bothnameanddependenciespropertieseggModulefield withnameproperty for standalone mode support
Note that PR #416 mentioned in the changelog specifically addressed adding eggModule declarations for module scanning, suggesting this field is functionally important for proper tegg module scanning.
📋 Proposed fix to add missing fields
"eggPlugin": {
- "name": "teggConfig"
+ "name": "teggConfig",
+ "dependencies": []
},
+ "eggModule": {
+ "name": "teggConfig"
+ },
"version": "3.74.0",If this plugin depends on other egg plugins, add them to the dependencies array.
As per coding guidelines: Plugin package.json files must include eggPlugin field with name and dependencies properties, and eggModule field with name property for standalone mode support.
📝 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.
| "eggPlugin": { | |
| "name": "teggConfig" | |
| }, | |
| "eggPlugin": { | |
| "name": "teggConfig", | |
| "dependencies": [] | |
| }, | |
| "eggModule": { | |
| "name": "teggConfig" | |
| }, |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@plugin/config/package.json` around lines 3 - 5, The package.json's eggPlugin
entry is missing the required "dependencies" property and the file lacks an
"eggModule" field; update the package.json to add eggPlugin.dependencies (an
array of plugin names or an empty array if none) alongside the existing
eggPlugin.name ("teggConfig"), and add an eggModule object with a "name"
property matching the module (e.g., "teggConfig") to support standalone module
scanning.
| "eggPlugin": { | ||
| "name": "mcpProxy" | ||
| }, |
There was a problem hiding this comment.
Plugin metadata is incomplete (eggPlugin.dependencies and eggModule missing).
Please add both required fields to satisfy plugin packaging requirements and standalone mode support.
🔧 Proposed fix
"eggPlugin": {
- "name": "mcpProxy"
+ "name": "mcpProxy",
+ "dependencies": [
+ "tegg"
+ ]
+ },
+ "eggModule": {
+ "name": "mcpProxy"
},As per coding guidelines, "Plugin package.json files must include eggPlugin field with name and dependencies properties, and eggModule field with name property for standalone mode support".
📝 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.
| "eggPlugin": { | |
| "name": "mcpProxy" | |
| }, | |
| "eggPlugin": { | |
| "name": "mcpProxy", | |
| "dependencies": [ | |
| "tegg" | |
| ] | |
| }, | |
| "eggModule": { | |
| "name": "mcpProxy" | |
| }, |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@plugin/mcp-proxy/package.json` around lines 4 - 6, Update the package.json's
eggPlugin metadata to include a dependencies property and add an eggModule entry
for standalone mode: inside the existing "eggPlugin" object (currently
containing "name": "mcpProxy") add a "dependencies" property (an object listing
any plugin deps or an empty object if none), and add a top-level "eggModule"
object with a "name" property (typically the package/plugin name, e.g.,
"mcpProxy"); ensure the property names are spelled exactly as
eggPlugin.dependencies and eggModule.name.
jerryliang64
force-pushed
the
worktree-release-v3.74.0
branch
from
fbfeed8 to
8dcebaf
Compare
1 participant
Summary
Test plan
🤖 Generated with Claude Code
Summary by CodeRabbit