Remove axios vulnerability #703
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.
Axios vulnerability
Oke! So this was a tricky one.
Problem analysiss
axiosis used bymeilisearch< v0.14docs-searchbar.jsusesmeilisearch.vuepress-plugin-meilisearchuses docs-searchbar.js. It uses the last version of docs-searchbar.jsv1.1.10. Which uses meilisearchv0.17.0which do NOT useaxios.So the 1 million question. Why with the latest version of
vuepress-plugin-meilisearchdo we still haveaxiosas a dependency of dependencies?What is going on in yarn.lock
Because the version of docs-searchbar that changed from meilisearch v0.12 to v0.14 was a patch change
1.1.7>1.1.8, and because we are giving as information^1.1, yarn.lock of documentation had no need to update the dependency.Solution
I removed and re-installed
vuepress-plugin-meilisearchso that it would download the latests version of all dependency.This made the yarn.lock change to the following: