fix: remove nodejs from extended tools to prevent conflict #16
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
nodejs_22from the extended tools list to prevent conflicts with system-installed nodejsProblem
The clawdbot package bundles
nodejs_22in its extended tools (nix/tools/extended.nix), which conflicts with system-installed nodejs when both are inhome.packages:Solution
Remove
nodejs_22from thebaseNameslist inextended.nix. Theclawdbot-gatewaywrapper already references node internally viamakeWrapperwith$NODE_BIN, so there's no need to expose node in the user's PATH through the tools bundle.Clawdbot continues to work correctly because:
makeWrapperto reference nodejs internallyFixes #15