Fix vulnerabilities and update other dependencies that don't break tests #176
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.
(Fixes #175)
NPM reports multiple vulnerabilities, and many packages where pretty old in general. Did the following:
npm audit fix --force
, thennpm test
to ensure all tests still passed (commit 8e97a1d).npm up
, thennpm test
to ensure all test still passed (commit c2dd2c8).npm outdated
and manually updated all packages tolatest
that didn't break test or changeeslint
output (commit 5d8f2ce).Only package that broke tests when manually updated was
async
. Didn't updateeslint
related packages since they causednpx eslint .
to report errors it wasn't reporting before.Tested plugin with personal
serverless
project and everything seems to be working as expected.