Memo: Research publishing the opencode v2 plugin to the npm registry #21

New Issue

2026-10-04T10:15:33Z

haylan commented

2026-10-04 10:15:33 +00:00

Goal: Research how to publish this opencode v2 plugin to the public npm registry, then extend the repository's release pipeline to publish it to npm.

Reference: https://docs.npmjs.com/about-the-public-npm-registry

Open questions to research:

Package name (scoped or not, check name availability on npm)
package.json fields / files included in the published tarball
Auth: npm token for the release pipeline (secret management)
npm publish specifics: 2FA / provenance / --provenance support in the pipeline
Whether the release pipeline (tags/CI) can be extended with a publish step, or needs a separate trigger

Outcome: A working pipeline extension that publishes the plugin to npm on release.

Requested 2026-10-04.

**Goal:** Research how to publish this opencode v2 plugin to the public npm registry, then extend the repository's release pipeline to publish it to npm. Reference: https://docs.npmjs.com/about-the-public-npm-registry **Open questions to research:** - Package name (scoped or not, check name availability on npm) - `package.json` fields / files included in the published tarball - Auth: npm token for the release pipeline (secret management) - `npm publish` specifics: 2FA / provenance / `--provenance` support in the pipeline - Whether the release pipeline (tags/CI) can be extended with a publish step, or needs a separate trigger **Outcome:** A working pipeline extension that publishes the plugin to npm on release. Requested 2026-10-04.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: haylan/fastcrw-opencode-websearch#21