You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-`path` mode installs successfully, then fails to resolve the plugin module from the cache path.
21
+
-`tarball` mode fails during install because the runtime appends `@latest` to the tarball `file:` spec.
22
+
- After the tarball install failure, the runtime falls back to the repo-level path plugin from `opencode.json`, which then reproduces the same path-resolution failure.
23
+
24
+
## Evidence
25
+
26
+
Run the smoke test and inspect the artifact directory printed in the JSON output under `.opencode/runtime-plugin-smoke/`.
27
+
28
+
Key log lines to expect:
29
+
30
+
- Path mode logs a `file:/.../plugin/gateway-core@latest` install, then `Cannot find module ...node_modules/file:/.../plugin/gateway-core`.
31
+
- Tarball mode logs a `file:/...my_opencode-gateway-core-0.1.1.tgz@latest` install attempt and fails with exit code `1`.
32
+
- Tarball mode then falls back to the repo path plugin and reproduces the same `Cannot find module` resolution failure.
33
+
34
+
## Impact
35
+
36
+
- Patched gateway runtime code in this repo cannot be validated end-to-end through `opencode serve` using local plugin specs.
37
+
- Gateway audit evidence such as `gateway_runtime_bootstrap` is absent because the patched plugin never loads.
38
+
39
+
## Expected behavior
40
+
41
+
- Local `file:` directory plugins should load after install without resolving through an invalid `node_modules/file:/...` module path.
42
+
- Local `file:` tarball plugins should install exactly as specified, without appending `@latest`.
0 commit comments