Fixed vulnerabilities with ipfs and mocha #693
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.
Proposed changes
This PR fixes vulnerabilities through
npm audit fix --force
After this PR, there is not any vulnerabilities issue.
Update
ipfs-http-client
libraryThe latest ipfs library only supports ESM (please refer to this).
Since the logic is changed to load ipfs with dynamic import function,
caver.ipfs.setIPFSNode
is changed to async function.This is a breaking change, so i write down it in the release notes.
Update
mocha
libraryThe bin file name is changed, so i updated path in
package.json
file for running test code.Types of changes
Please put an x in the boxes related to your change.
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
Related issues
closes #676
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...