Skip to content

fix(opencode-plugin): move bundled workspace dep to devDependencies#169

Merged
backnotprop merged 1 commit intobacknotprop:mainfrom
rcdailey:fix/opencode-plugin-workspace-dep
Feb 21, 2026
Merged

fix(opencode-plugin): move bundled workspace dep to devDependencies#169
backnotprop merged 1 commit intobacknotprop:mainfrom
rcdailey:fix/opencode-plugin-workspace-dep

Conversation

@rcdailey
Copy link
Contributor

@rcdailey rcdailey commented Feb 21, 2026

Problem

@plannotator/opencode@0.8.3 is broken for all consumers. Installing it via npm/bun fails with BunInstallFailedError because the published package.json contains a workspace:* dependency on @plannotator/server, which is unresolvable outside the monorepo.

The regression was introduced in #162 (commit 3a9a38e), which added "@plannotator/server": "workspace:*" to dependencies. Prior versions (0.8.2 and earlier) did not have this dependency and installed correctly.

Fix

Move @plannotator/server from dependencies to devDependencies. This is safe because the build script already bundles it into dist/index.js (only @opencode-ai/plugin is externalized via --external), so consumers never need to resolve it at install time.

Verified the full build (bun run build) still succeeds with this change.

The workspace:* protocol is unresolvable outside the monorepo, causing
BunInstallFailedError for npm consumers. Since the build bundles
@plannotator/server into dist/index.js rather than externalizing it,
the dependency is build-time only and belongs in devDependencies.
@backnotprop backnotprop merged commit e1d21f8 into backnotprop:main Feb 21, 2026
@rcdailey rcdailey deleted the fix/opencode-plugin-workspace-dep branch February 21, 2026 20:18
@backnotprop
Copy link
Owner

Thanks and sorry about that @rcdailey

Patch is in 0.8.5

@rcdailey
Copy link
Contributor Author

No problem, glad I could help. And thank you for the quick turnaround on the merge.

Unrelated: I noticed your release workflow only builds binaries and creates GitHub releases but doesn't publish to npm. Is that intentional? Happy to contribute a workflow for automated npm publishing if that'd be useful.

@backnotprop
Copy link
Owner

@rcdailey it's not intentional... just lazy with npm auth stuff. Lmk your thoughts and what you would need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants