fix(plugins): remove workspace:* from extension dependencies#11454
Closed
AnonO6 wants to merge 2 commits intoopenclaw:mainfrom
Closed
fix(plugins): remove workspace:* from extension dependencies#11454AnonO6 wants to merge 2 commits intoopenclaw:mainfrom
AnonO6 wants to merge 2 commits intoopenclaw:mainfrom
Conversation
…w#10941, openclaw#11245) Four extensions had "openclaw": "workspace:*" in dependencies (not just devDependencies). When plugins are installed outside the pnpm workspace (e.g., via `openclaw plugins install ./extensions/feishu`), npm cannot resolve the workspace: protocol and fails with EUNSUPPORTEDPROTOCOL. Remove openclaw from dependencies in: - extensions/zalo/package.json - extensions/zalouser/package.json - extensions/nostr/package.json - extensions/msteams/package.json The openclaw reference remains in devDependencies (for workspace-local development) and runtime resolution works via the jiti alias, per CLAUDE.md guidance. Closes openclaw#10941 Closes openclaw#11245 Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
bob10042
pushed a commit
to bob10042/openclaw
that referenced
this pull request
Feb 14, 2026
…-plugin feat: Add frontend-design plugin to marketplace
bfc1ccb to
f92900f
Compare
|
This pull request has been automatically marked as stale due to inactivity. |
3 tasks
Contributor
|
Closing as AI-assisted stale-fix triage. Linked issue #10941 ("[Bug]: Local plugin(飞书 feishu) installation fails due to unhandled workspace: protocol in package.json") is currently CLOSED and was closed on 2026-02-13T03:28:14Z with state reason NOT_PLANNED. If the underlying bug is still reproducible on current main, please reopen this PR (or open a new focused fix PR) and reference both #10941 and #11454 for fast re-triage. |
Contributor
|
Closed after AI-assisted stale-fix triage (closed issue duplicate/stale fix). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #10941, Fixes #11245
Four extensions had
"openclaw": "workspace:*"independencies(not justdevDependencies). When plugins are installed outside the pnpm workspace (e.g.,openclaw plugins install ./extensions/feishu), npm cannot resolve theworkspace:protocol and fails withEUNSUPPORTEDPROTOCOL.lobster-biscuit
Repro Steps
openclaw plugins install ./extensions/zalo(or nostr, msteams, zalouser)~/.openclaw/extensions/npm install --omit=devruns in the plugin dirError: Unsupported URL Type "workspace:": workspace:*Root Cause
These 4 extensions had
"openclaw": "workspace:*"independencies:extensions/zalo/package.jsonextensions/zalouser/package.jsonextensions/nostr/package.jsonextensions/msteams/package.jsonThe
workspace:*protocol is a pnpm workspace feature. When the plugin is copied outside the workspace for installation, npm doesn't understandworkspace:*and errors out. Per CLAUDE.md: "Avoidworkspace:*independencies(npm install breaks); putopenclawindevDependenciesorpeerDependenciesinstead (runtime resolvesopenclaw/plugin-sdkvia jiti alias)."Most other extensions (telegram, discord, slack, matrix, etc.) already follow this pattern correctly — only these 4 had the bug.
Behavior Changes
"openclaw": "workspace:*"fromdependenciesin 4 extensionsdevDependenciesentry remains (for workspace-local development)Codebase and GitHub Search
workspace:*across allextensions/*/package.json— found 4 with it independenciesextensions/memory-coreuses the correct pattern (devDependencies+peerDependencies)workspace:*independenciesTests
pnpm build✓pnpm check✓Sign-Off
Made with Cursor
Greptile Overview
Greptile Summary
This PR updates four extension
package.jsonfiles (msteams,nostr,zalo,zalouser) to remove"openclaw": "workspace:*"fromdependencieswhile keeping it indevDependencies.This aligns these extensions with the existing plugin packaging pattern in the repo: extensions are installed outside the pnpm workspace (via
openclaw plugins install ...) and therefore must not rely on the pnpm-onlyworkspace:protocol at runtime install time. Keepingopenclawonly as a dev dependency preserves local workspace development while allowingnpm install --omit=devto succeed when extensions are copied to~/.openclaw/extensions/.Confidence Score: 5/5
workspace:*dependency specifier from runtimedependenciesin four extensions; this directly fixesnpm install --omit=devoutside the workspace and does not affect runtime code paths. The remainingdevDependenciesentry preserves local development behavior.(4/5) You can add custom instructions or style guidelines for the agent here!
Context used:
dashboard- CLAUDE.md (source)dashboard- AGENTS.md (source)