chore: update package dependencies #752
Merged
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
broofa
requested review from
pmccarren and
ctavan
and removed request for
pmccarren
ctavan
approved these changes
Jun 4, 2024
|
/me grants @broofa two extra hours of life and asks for forgiveness – will try to make up for it |
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.
Updating all out-of-date
[dev]dependencies. The two major ones areeslintandprettier.This also switches to
eslint's flat config file format, which is always a "fun" exercise. On this occasion, because we're using StandardJS, I ran into this issue. And I guess there's some opensource clownery going on in that project where the current published version ofeslint-config-standardis broken but there's some debate over governance or... something? I dunno, I spent way too much time trying to figure out what was broken, and then why it can't be fixed, and then why the project had to be forked, then trying to figure out how to get the fork of the project working here.And if anyone from StandardJS or NeoStandard ends up reading this... I WANT THE LAST TWO HOURS OF MY LIFE BACK, PLEASE!