Fix the vulnerability in the yaml
NPM package
#3640
Merged
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.
Closes #3637
Upgraded the
yaml
package to version 2.2.2 to resolve the vulnerability, reported by Snyk.Added an alias for the
yaml
package inpackage.json
to resolve the ReferenceError happening in v2.2.2 with the default import. Parcel chokes on mixed types of exports (probably where export all/export with rename are mixed, as stated in the following issue $78fb23f46eb09f80$exports is not defined parcel-bundler/parcel#8792 ).Updated the
@docusaurus
package and its dependencies. Added a custom resolution foryaml
v2.2.2 to website subdependencies.Tested:
npm run build
to make sure it builds successfully.yarn start
.Testing:
To test it, run the app in Tilt and make sure that there are no errors displayed in the browser console in general or on object detail pages when displaying YAML views.