Repository navigation
v1.0.0-alpha.7
Pre-release
Pre-release
·
11 commits
to main
since this release
Changed
- Widened the
@opencode/pluginpeer range from^2.0.15to^2.0.3, matching what the kit actually supports. Verified by typecheck and the type-tripwire against 2.0.3, 2.0.10 and 2.0.18. 2.0.3 is the floor: earlier 2.x releases ship no./tuisubpath export, so nothing importing@opencode/plugin/tuican resolve it. - Documented the 2.0.3 floor in the Compatibility section.
CollapsibleSectionandCollapsibleGrouptake an optionalthemeprop, so a consumer can hand down the host's ownusePlugin().themeinstead of the kit reaching for the plugin context itself.
Fixed
CollapsibleSection/CollapsibleGroupno longer throwPluginContextProvider is missingwhen the kit is installed fromnode_modules. Both calledusePlugin()unconditionally, but a registry install resolves a different copy of@opencode/pluginandsolid-jsthan the one the host renders with, so the host's plugin context was never visible. Callers that already hold the context passthemedown; theusePlugin()fallback still resolves for deduped module graphs (tests, monorepos) and degrades to unthemed text rather than throwing.
Install
npm install opencode-plugin-kitlatest now points at this release, so a plain install gets the v2 kit. The
publish workflow tags each prerelease under its own identifier and leaves
latest alone, so later alphas will not move it automatically — install
opencode-plugin-kit@alpha to track the newest build.
Consumer action required
If you render a collapsible sidebar section, pass the host theme:
const { theme } = usePlugin()
<CollapsibleSection title="..." count={n} theme={theme}>...</CollapsibleSection>