Solve critical vulnerability of Presto UI from @babel/traverse
npm package
#21322
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.
Ref: #21319
Description
Update @babel and related packages to newer versions to solve the critical vulnerability issue reported by
yarn audit
: GHSA-67hx-6x53-jw92Motivation and Context
The critical vulnerability issue reported by
yarn audit
may impact servers that run the babel to compile the Presto UI code or developers' machines. Although there is nopath.evaluate()
orpath.evaluateTruthy()
in the current code base, it's good to fix it.Impact
Most of the JS files are not changed, except
query.js
.Test Plan
Manually run the Presto UI and verify the query page.
Contributor checklist
Release Notes
Please follow release notes guidelines and fill in the release notes below.