chore: Update dependencies #38
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
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.
Resolves #32. There is one major version change with
eslint-plugin-unicorn, however there doesn't appear to be anything affecting us (lint seems fine). Smoke tested rendering & notable actions (particularly the image carousel) locally.Tracing through a warning in lint (which I now can't replicate?), it seems like
@typescript-eslintdeps are being kept onv6.9rather thanv6.14(latest). I don't see any reason why this would be the case, so question for the future. It is highly unfortunate that npm has poor (if any) support for managing/updating transitive dependencies.