Bump node-fetch and eosjs in /Worlds-Engine
Removes node-fetch. It's no longer used after updating ancestor dependency eosjs. These dependencies need to be updated together.
Removes node-fetch
Updates eosjs from 16.0.8 to 22.1.0
Release notes
Sourced from eosjs's releases.
EOSJS v22.1.0 Release Notes
This release is the stable release of EOSJS v22.1.0 and contains features, security, stability and miscellaneous fixes.
Support for Read Only Transactions
This release introduces support for the new feature of read only transactions within smart contracts. This feature provides a contract-supported method of read-only queries from external clients via HTTP-RPC. Prior to this release, access was limited to data stored in a single table in DB or KV tables via the
get_table_rowsorget_kv_table_rowsAPI, a mechanism which is exacting and inefficient. Read-only queries enable developers to perform more complex, cross-table queries natively via contract code with the assurance that table data is from the same block height. It can also be used to understand the consequences of a transaction before it is sent. More information can be found here in the documentation for cleos and here in the documentation specific to eosjs.The
transaction_tracehas been modified with the addition of abill_to_accountsfield, so that it is clear which account paid for cpu/net for the transaction. Additionally, in the case of a failed transaction, available traces are returned to assist in the understanding of why the transaction failed. You can find the failure traces by using the newdetailsfield in the RPCError object.An example transaction using eosjs might look like:
await api.transact({ actions: [{ account: 'readonly', name: 'get', authorization: [{ actor: 'readonly', permission: 'active', }], data: {}, }], }, { useLastIrreversible: true, expireSeconds: 30, readOnlyTrx: true, returnFailureTraces: true, });The above transaction calls this action that is able to retrieve entries in two tables instead of needing to run
get_kv_table_rowsmultiple times:[[eosio::action, eosio::read_only]] std::vector<my_struct> get() { my_table_m tm{get_self()}; my_table_f tf{get_self()};std::vector<my_struct> ret; auto itm = tm.id.begin(); auto itm_e = tm.id.end(); eosio::cout << "Males: \n"; while(itm != itm_e){ auto row = itm.value(); eosio::cout << "id=" << row.id << ", name=" << row.name << ",gender=" << row.gender << ", age=" << row.age << "\n"; my_struct s; s.id = row.id; s.name = row.name; s.gender = row.gender; s.age = row.age; ret.push_back(s); ++itm; </tr></table>
... (truncated)
Commits
1fa93d4Merge pull request #992 from EOSIO/release/22.1.x9ccdb11Merge pull request #994 from EOSIO/merging_master370b9e8Updating package.json and yarn.lockd6842b6Merge branch 'master' into merging_masterf05d9e8Merge pull request #993 from EOSIO/updating_cicd_docker_image50dc670Updating package.json and yarn.lock7147a05Updating CI/CD to latest version before merging into developea34fb9Merge pull request #988 from EOSIO/updating_cicd_for_releasea1fbfb3Updating default branch with new ci/cd and dependabot settingsf29efffMerge pull request #976 from EOSIO/dependabot/github_actions/develop/docker/s...- Additional commits viewable in compare view
Maintainer changes
This version was pushed to npm by b1serviceaccount, a new releaser for eosjs since your current version.
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.