chore: update log4js to 3.0.0 #3078
Closed
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
|
Looks like fixing this will require dropping node 4, which probably means a major version bump 😞 |
|
Node.js 4 is no longer supported upstream. Also, log4js 2.x (through its loggly dependency) includes quite a few exploitable packages which users (like me) have started to get notices about. Not that any of that helps the major version # bump, but it could serve to justify it. |
|
We also have issues with loggly's dependencies. It pulls in [email protected] from 2016, which includes the dependency "[email protected]" that does not name the license in package.json making it hard to review licenses. |
|
Obselete by #3082 |
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.
No description provided.