[exa-mcp-server]: fix npx bin resolution by renaming .smithery/ to smithery/ #175
Conversation
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
…solution npm's securePath in @npmcli/package-json strips bin paths starting with a dot, causing npx -y exa-mcp-server to fail with 'could not determine executable to run'. Fixes #107. Co-Authored-By: ishan@exa.ai <ishan@exa.ai>
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:
|
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
npx -y exa-mcp-serverfails withcould not determine executable to runbecause npm'ssecurePath(in@npmcli/package-json) returns empty string for any bin path starting with.— the.smithery/stdio/index.cjsbin target gets silently deleted during package normalization, so npx never finds an executable.Fix: rename
.smithery/→smithery/in all 5 files that reference it. No other changes.Fixes #107.
Review & Testing Checklist for Human
npm pack, thennpx /path/to/exa-mcp-server-<version>.tgz— confirm the bin resolves and the server starts. This is the only way to verify the fix actually works since there's no automated test for it.npm run buildstill outputs tosmithery/: the smithery CLI respects the-oflag so this should work, but confirm the build artifacts land correctly.npm publishafter merging — existing 3.1.7 installs remain broken until a new version hits the registry.Notes
ENTRYPOINTreferencessmithery/index.cjs(notsmithery/stdio/index.cjs) — this matches pre-existing behavior and was not changed.