fix: rename .smithery to smithery to fix npx executable resolution#172
Open
devin-ai-integration[bot] wants to merge 1 commit intomainfrom
Open
fix: rename .smithery to smithery to fix npx executable resolution#172devin-ai-integration[bot] wants to merge 1 commit intomainfrom
devin-ai-integration[bot] wants to merge 1 commit intomainfrom
Conversation
npm's package normalization (securePath in @npmcli/package-json) rejects bin paths starting with a dot, causing the bin field to be stripped from the manifest. This made 'npx -y exa-mcp-server' fail with 'could not determine executable to run'. Fixes #49 Co-Authored-By: unknown <>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
Author
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
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.
fix: rename .smithery to smithery to fix npx executable resolution
Summary
Fixes #49 —
npx -y exa-mcp-serverfails withnpm error could not determine executable to run.Root cause: npm's package normalization (
securePathin@npmcli/package-json) strips anybinpath that starts with a dot. The path.smithery/stdio/index.cjsgets normalized to an empty string, the bin entry is deleted, and npx can't find an executable to run.Fix: Rename the build output directory from
.smitherytosmitheryacross all references:package.json(bin, files, build scripts),.gitignore,.vercelignore,Dockerfile,tsconfig.json, andpackage-lock.json.Review & Testing Checklist for Human
npm publishruns.npm pack, thennpx /path/to/exa-mcp-server-<version>.tgzto confirm the bin resolves correctly before publishing.docker build .still works — the Dockerfile paths were updated but this wasn't tested..smitherythat weren't updated here.Notes
ENTRYPOINTreferencessmithery/index.cjs(notsmithery/stdio/index.cjs). This matches the pre-existing behavior and was not changed by this PR.