docs: switch mcp-bridge invocation from node to deno run -A#45
Merged
hyperpolymath merged 1 commit intomainfrom May 2, 2026
Merged
docs: switch mcp-bridge invocation from node to deno run -A#45hyperpolymath merged 1 commit intomainfrom
hyperpolymath merged 1 commit intomainfrom
Conversation
mcp-bridge/main.js uses Deno APIs (Deno.env.get, Deno.stdin.readable, Deno.exit) and ships a deno.json config, but README.md, README.adoc, docs/index.html, and package.json#start all told users to launch it with node, causing ReferenceError: Deno is not defined on first install. https://claude.ai/code/session_01G9pKozzr5GYMkAC9NgqUju
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
mcp-bridge/main.jsis a Deno program (usesDeno.env.get,Deno.stdin.readable,Deno.exit— confirmed via grep; shipsmcp-bridge/deno.jsonwith Deno task config). Several user-facing docs andpackage.json's"start"script told users to launch it withnode, producingReferenceError: Deno is not definedon first install.This came from a 2026-04-30 install session where the maintainer hit that exact error running
claude mcp add ... -- node ... mcp-bridge/main.jsper the README.Premise verification:
grep -n 'Deno\.' mcp-bridge/main.jsreturns lines 249, 496, 507 — confirmed Deno API usage.mcp-bridge/deno.jsonexists withdeno run --allow-net --allow-env --allow-read main.jsas its start task.Files changed
package.jsonscripts.startusednode mcp-bridge/main.js; changed todeno run -A mcp-bridge/main.jssonpm startworksREADME.mdclaude mcp add boj-server -- node mcp-bridge/main.jsREADME.adocnode /path/to/…), one relative (node mcp-bridge/main.js)docs/index.htmlnode /path/to/boj-server/mcp-bridge/main.jsTotal: 4 files, 5 lines changed (5 substitutions).
Deliberately left alone
mcp-bridge/main.jspackage.json→bin.boj-servernpx/npm-publish story for a Deno bridge needs its own decision; out of scope for this PRpackage.json→scripts.test(node --test …)dispatch_test.js; separate from bridge invocationREADME.adocline 107 (node --test mcp-bridge/tests/)package.json→engines.nodeenginesblock left as-isdocs/practice/DOGFOOD-LOG.adocline 149/usr/bin/nodebug; editing a log entry would falsify the recordHow to test
No more
ReferenceError: Deno is not defined.Generated by Claude Code