fix: resolve commands directory path for both bundled and dev environments #3
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
…ments The path resolution in command-installer.ts was incorrect after bundling. When all code is bundled into dist/index.js, the relative path "../.." went too far up the directory tree. - Add findCommandsDir() to try multiple candidate paths - Support both production (dist/index.js) and development (src/config/) - Remove unnecessary warning log when directory not found - Bump version to 0.1.2 Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Owner
Author
|
local: ok |
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
command-installer.tsthat was broken after bundlingfindCommandsDir()function to try multiple candidate pathsdist/index.js) and development (src/config/) environmentsBackground
When all code is bundled into
dist/index.js, the relative path"../.."went too far up the directory tree, causing the commands directory to not be found. The fix tries multiple paths in order:../commands(for bundled production)../../commands(for development)Test plan
~/.config/opencode/command/on plugin initialization🤖 Generated with Claude Code