fix: move @types/component-emitter to dependencies #99
Conversation
This file contains 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
Otherwise consumers of socket.io-parser (and socket.io) need to have it listed in their devDependencies. Signed-off-by: Pascal Sthamer <[email protected]>
|
Thanks! Regarding the audit, most of the issues comes from |
|
Included in 4.0.2. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Otherwise consumers of socket.io-parser (and socket.io) need to have it listed in their devDependencies.
While doing this I noticed that
npm auditreported a lot of issues. It might be worth to upgrade dependencies.Signed-off-by: Pascal Sthamer [email protected]