[Snyk] Upgrade web3-providers-ipc from 1.8.2 to 1.10.0 #218
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.
Snyk has created this PR to upgrade web3-providers-ipc from 1.8.2 to 1.10.0.
ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.
Release notes
Package name: web3-providers-ipc
-
1.10.0 - 2023-05-10
- Improved the error propagation in
- Fixed "Uncaught TypeError" calling a contract function that revert using MetaMask (#4454) and related "n.data.substring is not a function", that is raised when there is a revert and
- When sending a transaction, if
- Removed an unnecessary
- Added support for
- Updated dependencies (#6044)
-
1.10.0-rc.0 - 2023-05-02
- Improved the error propagation in
- Fixed "Uncaught TypeError" calling a contract function that revert using MetaMask (#4454) and related "n.data.substring is not a function", that is raised when there is a revert and
- When sending a transaction, if
- Removed an unnecessary
- Added support for
- Updated dependencies (#6044)
-
1.9.0 - 2023-03-20
- Fixed skipped ws-ganache tests (#5759)
- Fixed "provider started to reconnect error" in web3-provider-ws (#5820)
- Fixed Error: Number can only safely store up to 53 bits (#5845)
- Fixed types for packages which have default exports but not declared default export in .d.ts (#5866)
- Fixed Transaction type by adding missing properties (#5856)
- Add optional
- Updated @ types/bn.js dependency to 5.1.1 in web3, web3-core and web3-eth-contract as reason mentioned in #5640 (#5885)
- Add description to error for failed connection on websocket (#5884)
- Updated dependencies (#5885)
-
1.9.0-rc.0 - 2023-03-07
- Fixed skipped ws-ganache tests (#5759)
- Fixed "provider started to reconnect error" in web3-provider-ws (#5820)
- Fixed Error: Number can only safely store up to 53 bits (#5845)
- Fixed types for packages which have default exports but not declared default export in .d.ts (#5866)
- Fixed Transaction type by adding missing properties (#5856)
- Add optional
- Updated @ types/bn.js dependency to 5.1.1 in web3, web3-core and web3-eth-contract as reason mentioned in #5640 (#5885)
- Add description to error for failed connection on websocket (#5884)
- Updated dependencies (#5885)
-
1.8.2 - 2023-01-30
- Updated Webpack 4 to Webpack 5, more details at (#5629)
- Updated
- Updated
- Bump utils 0.12.0 to 0.12.5 (#5691)
- Fixed types for
- Fixed Next.js builds failing on Node.js v16, Abortcontroller added if it doesn't exist globally (#5601)
- Builds fixed by updating all typescript versions to 4.1 (#5675)
- Add
from web3-providers-ipc GitHub release notesFixed
web3-providers-httppackage to effectively propagate useful error infomation about failed HTTP connections (#5955)web.eth.handleRevert = true(#6000)Changed
transaction.typeis now formatted to a hex string before being send to provider (#5979)transaction.type === '0x1' && transaction.accessList === undefined, thentransaction.accessListis set to[](#5979)chainIdparameter fromtoChecksumAddress()function types (#5888)Added
getPastEventsmethod to filterallEventsand specific event (#6015)Security
Fixed
web3-providers-httppackage to effectively propagate useful error infomation about failed HTTP connections (#5955)web.eth.handleRevert = true(#6000)Changed
transaction.typeis now formatted to a hex string before being send to provider (#5979)transaction.type === '0x1' && transaction.accessList === undefined, thentransaction.accessListis set to[](#5979)chainIdparameter fromtoChecksumAddress()function types (#5888)Added
getPastEventsmethod to filterallEventsand specific event (#6015)Security
Fixed
Changed
hexFormatparam togetTransactionandgetBlockthat accepts the value'hex'(#5845)utils.toNumberandutils.hexToNumbercan now return the large unsafe numbers asBigInt, iftruewas passed to a new optional parameter calledbigIntOnOverflow(#5845)Security
Fixed
Changed
hexFormatparam togetTransactionandgetBlockthat accepts the value'hex'(#5845)utils.toNumberandutils.hexToNumbercan now return the large unsafe numbers asBigInt, iftruewas passed to a new optional parameter calledbigIntOnOverflow(#5845)Security
Changed
crypto-browserifymodule is now used only in webpack builds for polyfilling browsers (#5629)ethereumjs-utilto7.1.5(#5629)lerna4 to version 6 (#5680)Fixed
web3.utils._jsonInterfaceMethodToString(#5550)Removed
clean-webpack-pluginhas been removed from dev-dependencies (#5629)Added
https-browserify,process,stream-browserify,stream-http,crypto-browserifyadded to dev-dependencies for polyfilling (#5629)readable-streamto dev-dependancies for webpack (#5629)Security
npm audit fixfor libraries update (#5726)Commit messages
Package name: web3-providers-ipc
transaction.typeto hex. Add emptyaccessLististx.type === '0x1'web3/web3.js#5979)hextogetTransactionandgetBlock. web3/web3.js#5845)Compare
Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs