Skip to content

registry: add magpie-muse-web-connector (Muse Web connector) - #1317

Open
JohnWangggg wants to merge 1 commit into
magpie-community:mainfrom
JohnWangggg:add-muse-web-connector
Open

JohnWangggg wants to merge 1 commit into
magpie-community:mainfrom
JohnWangggg:add-muse-web-connector

Conversation

@JohnWangggg

Copy link
Copy Markdown

Adds magpie-muse-web-connector (muse-web) to the market.

What it is

A connector edition of the full magpie-muse-web plugin. It does not start a browser, does not read cookie files and does not spawn a process. It talks over loopback HTTP to a muse-web engine the user runs separately (the engine from the full package). Sign-in can go through that engine (POST /v1/login + poll) or use an account ID from GET /v1/accounts.

Why a separate package

The full edition bundles the engine and launches Chrome, which the repo's harm rules do not allow in a market package. This connector is the trimmed edition; the full edition stays on GitHub/npm (magpie-muse-web). Both use the same provider id muse-web, so users install one, not both.

Details

  • npm: magpie-muse-web-connector@0.1.0
  • repo: https://github.com/JohnWangggg/magpie-muse-web/tree/main/connector
  • registry entry: provider muse-web, icon from the repo
  • engine: magpie-muse-web@0.6.1+, or node engine/main.mjs from the repo
  • tests: 6 contract tests in connector/contract.test.mjs; the root repo also runs them in a three-OS CI
  • no cookie read, no process started by the plugin itself

@JohnWangggg

Copy link
Copy Markdown
Author

Status: both packages are live on npm — magpie-muse-web@0.6.1 and magpie-muse-web-connector@0.1.0. bun scripts/check.mjs passes in the fork, and the only changed file is registry.json (+2 lines). The pr workflow is currently action_required because this is a first-time contributor; a maintainer needs to approve the run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant