[exa-mcp-server]: Fix npx executable resolution by moving build output from hidden .smithery/ to smithery/ #156
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
…hery/ directory npx fails to resolve the executable because npm cannot create symlinks to files in dot-prefixed (hidden) directories. Renaming .smithery/ to smithery/ fixes the bin resolution for npx -y exa-mcp-server. Fixes #107 Co-Authored-By: unknown <>
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.
Fix npx executable resolution by renaming hidden
.smithery/tosmithery/Summary
Fixes #107.
npx -y exa-mcp-serverfails because npm cannot create symlinks innode_modules/.bin/when thebintarget path is inside a dot-prefixed (hidden) directory (.smithery/).This PR renames all references from
.smithery/→smithery/across the repo. The change is purely a directory rename — no logic, build, or runtime behavior changes.Files changed:
package.json,package-lock.json,Dockerfile,tsconfig.json,.gitignore,.vercelignoreReview & Testing Checklist for Human
npxresolution works after publish: Build passes locally, but the actual fix can only be fully confirmed after an npm publish. Consider runningnpm packand testing the tarball withnpxto simulate.ENTRYPOINT ["node", "smithery/index.cjs"]usessmithery/index.cjs(no subdirectory), while build outputs go tosmithery/stdio/index.cjsandsmithery/shttp/index.cjs. This is a pre-existing issue not introduced by this PR — just preserved as-is..smitheryreferences that may have been missed.Notes