Problem
The postinstall.mjs script in packages/opencode/script/postinstall.mjs hardcodes the platform-specific binary package name as opencode-${platform}-${arch} (unscoped). When the package is published under an npm scope (e.g. @vibetechnologies/opencode), the postinstall fails with:
Failed to setup opencode binary: Could not find package opencode-linux-x64: Cannot find module 'opencode-linux-x64/package.json'
The platform-specific packages published from a scoped fork get scoped names too (@vibetechnologies/opencode-linux-x64), but the postinstall never prepends the scope.
Root Cause
packages/opencode/script/postinstall.mjs:52 — constructs opencode-${platform}-${arch} without considering the npm scope.
Fix
Read the package's own package.json, extract the scope (text before the last /), and prepend it when constructing the platform package name. This works for both unscoped packages (opencode-linux-x64) and scoped ones (@vibetechnologies/opencode-linux-x64).
Labels
bug, build
Problem
The
postinstall.mjsscript inpackages/opencode/script/postinstall.mjshardcodes the platform-specific binary package name asopencode-${platform}-${arch}(unscoped). When the package is published under an npm scope (e.g.@vibetechnologies/opencode), the postinstall fails with:The platform-specific packages published from a scoped fork get scoped names too (
@vibetechnologies/opencode-linux-x64), but the postinstall never prepends the scope.Root Cause
packages/opencode/script/postinstall.mjs:52— constructsopencode-${platform}-${arch}without considering the npm scope.Fix
Read the package's own
package.json, extract the scope (text before the last/), and prepend it when constructing the platform package name. This works for both unscoped packages (opencode-linux-x64) and scoped ones (@vibetechnologies/opencode-linux-x64).Labels
bug, build