feat: update dependencies #933
Merged
Conversation
This file contains hidden or 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
|
|
samrichardsontylertech
approved these changes
May 30, 2025
|
🚀 PR was released in |
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.
I had to override the
@web/test-runner-chromedependency because of this commit:modernweb-dev/web@79b0ba4
Any of our tests that call
.focus()on a custom element that propagates focus to a separate element were failing otherwise. Will keep an eye on any fixes or solutions.Storybook will be updated separately to v9 once a couple community plugins we use are released with compatible versions.
Additionally, I upgraded
sasswhich triggered the knownmixed-declsdeprecation warning that is coming in 2.0 eventually. This warning is very verbose, and is notifying us of potential breaking changes due to source order output changes from Sass. We should keep an eye on the feature request here that would enable us to opt-in to the new functionality early and validate if the changes cause problems for us without having to update 100s of lines of code now using the& { }syntax