Repository navigation
Add exports map so OpenCode 2 loader resolves the package entry - #52
Merged
Merged
Conversation
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
The OpenCode 2 plugin loader resolves published packages through the package
exportsmap (subpath"."= package root), not the legacymainfield. This package ships onlymain(dist/index.js), so the loader never reaches the module that holds the valid plugin default and fails with:This PR adds an
exportsmap pointing at the entry that already exposes the dual-shape default ({ id, server, setup }):The V1 plugin (
server) and the V2 entrypoint (setup) are both preserved in the default export — this change only makes the package resolvable by the OpenCode 2 loader.