fix: run npm install after extension copy in setup.sh#36
Open
fix: run npm install after extension copy in setup.sh#36
Conversation
plugins install copies extension files but doesn't install npm dependencies. After rm -rf of the extension dir, node_modules are lost and the plugin fails to load with "Cannot find module" errors. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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
1 participant
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
setup.sh syncdoesrm -rfon the extension dir then copies fresh files viaplugins install, but never runsnpm install@sinclair/typebox) after a fresh syncnpm install --productionstep after extension copyTest plan
./setup.sh syncon a fresh gateway install🤖 Generated with Claude Code