fix: workflow visualizer for npx execution#29
Merged
Merged
Conversation
- Add CLI wrapper script (bin/visualizer.js) to start dev server - Add bin entry to workflow-visualizer package.json - Include workflow-visualizer in main package files and bin - Add build:visualizer script to main package build process - Fix TypeScript compilation errors: - Add missing InteractionEvent type definition - Fix import paths for workflow types - Add plantuml-encoder type declaration - Fix D3.js type issues with undefined coordinates - Remove unused functions and parameters - Fix template literal syntax errors - Update main package to include workflow-visualizer as executable The visualizer can now be run via: - npx responsible-vibe-mcp workflow-visualizer (when published) - Local: npm run build && node workflow-visualizer/bin/visualizer.js
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.
The visualizer can now be run via: