chore: Update vite to 5.4.6 #66
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
coliu-akamai
force-pushed
the
update-vite
branch
from
3839cbe to
e93bfe7
Compare
coliu-akamai
force-pushed
the
update-vite
branch
from
e93bfe7 to
89f849e
Compare
jaalah-akamai
approved these changes
Sep 18, 2024
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.
Description 📝
We have a couple new security alerts (like CM) because of vite - bumping up vite here as well (see linode/manager#10960).
Major Changes 🔄
Testing
Confirm no breaking changes, no changes to the tokens when running
yarn generate(besides date changes)NOTE: there will still be a bunch of dependabot alerts - most of them seem to be due to storybook (it has the express dependency, and express has a lot of dependencies as well...) - will be keeping an eye on storybook to see when they update to take care of these security issues! (unless we want to update now, directly updating yarn.lock)