Debugging (read below) #4
Merged
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
…-estree'" by moving from devDependencies to dependencies (in package.json). Why: VibeSafe requires this package at runtime for scanning, but it was previously only installed for development. This caused errors when running the CLI as a global package. No new dependencies produced, just a moving it so that it worked. When I tried to run 'vibesafe scan' on my machine, I encountered this error.
ccozad
approved these changes
May 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Fixing this error: "Cannot find module '@typescript-eslint/typescript-estree'" by moving from devDependencies to dependencies (in package.json).
Why:
VibeSafe requires this package at runtime for scanning, but it was previously only installed for development. This caused errors when running the CLI as a global package.
No new dependencies produced, just a moving it so that it worked. When I tried to run 'vibesafe scan' on my machine, I encountered this error.
Btw... Love this project, and I hope to continue contributing! I vibecode all the time, and this will not only help me but help many others.