Skip to content

fix(build): mark nodejs-whisper external in MCP bundling #44

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
DannyNs merged 1 commit into from
Jun 18, 2026
Merged

fix(build): mark nodejs-whisper external in MCP bundling #44

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion scripts/build-mcp.mjs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,11 @@ const servers = [
"documentation",
];

const external = ["better-sqlite3", "node-pty"];
// Native / optional packages must not be inlined by esbuild. nodejs-whisper pulls in
// whisper.cpp and is an optional STT dependency that may be absent or fail to install;
// the voice provider imports it lazily and degrades gracefully at runtime. Bundling it
// makes the build fail with "Could not resolve 'nodejs-whisper'" when it is not present.
const external = ["better-sqlite3", "node-pty", "nodejs-whisper"];

// CJS packages bundled into ESM need a real require() for Node built-ins
const banner = `import { createRequire as __bundleCR } from "module"; const require = __bundleCR(import.meta.url);`;
Expand Down
Loading