Clean npm dependencies #1
Open
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
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.
First, thanks for this amazing library!
We are using
differenceequationsignal1din our LORIS EEG visualization component and have recently dealing with more than 40 security alerts for vulnerabilities introduced by outdated dependencies fromdifferenceequationsignal1d.differenceequationsignal1ddeclares an old version ofnpm-check-updatesas a dependency which requires more than 30 other dependencies that causes those issues. I propose to remove the dependency sincenpm-check-updatesis a tool that can be installed and run globally.