Upgrade node modules #994
Merged
Upgrade node modules #994
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
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.
Checklist
Some of the node modules in our tree are deprecated and/or out of date. I was not able to individually update them (I think using yarn workspaces is what makes this difficult) so instead I ran
yarn updatewhich updated every single package.In order to avoid deprecated packages in
@slack/clientI had to upgrade that to^4.0. According to the migration guide, there are no breaking changes in the way we use the library.Changelog Entry
Improvement - Upgraded all node modules
Closing issues
N/A