docs: bump npm dependencies to address component vulnerability risks - #984
Merged
Conversation
Update the website package versions for local search, React, and related frontend tooling. This keeps the Docusaurus site dependencies current with recent patch and minor releases.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Purpose of the pull request
Update the npm dependencies of the website and handle the npm component vulnerability risks in the Dependabot alerts.
What's changed?
pnpm-lock.yamlfile.After my local testing, I found that the
css-whatcomponent cannot be upgraded directly. We need to wait for@docusaurusto submit a new version before proceeding.Checklist