Tim Daubenschütz

https://github.com/ChainSafe/web3.js/issues/5350#issuecomment-1218277041 e.g. ethers js

ETHEREUM JSON RPC endpoints arguably support batching calls. So we should allow batching via the transport module - https://web3js.readthedocs.io/en/v1.2.11/web3-eth.html#batchrequest - https://sajya.github.io/docs/batch/ via alchemy docs: https://docs.alchemy.com/alchemy/documentation/batch-requests > Batch requests are single...

- https://github.com/rugpullindex/eth-fun/blob/master/src/call.js exports encodeEventSignature - but src/index.js doesn't

``` // Aggregating modules export * from …; // does not set the default export export * as name1 from …; // Draft ECMAScript® 2O21 export { name1, name2, …,...

``` npm i [email protected] --save-peer npm WARN EBADENGINE Unsupported engine { npm WARN EBADENGINE package: '[email protected]', npm WARN EBADENGINE required: { node: '~14.19.3', npm: '^6.14.17' }, npm WARN EBADENGINE current:...

Should we depreciate node v12 support and transpiling?

2

/cc @il3ven

e.g. see here: https://github.com/TimDaub/ERC721-wallet/blob/c5a73c78b600f0a94cd6f596fd8775319b4d4a62/__tests__/sagas/fetchTransactions.js#L14