Can't run after bundling with Webpack in AWS Lambda

[mazzio97]

Ethers Version

5.6.9

Search Terms

No response

Describe the Problem

If I zip the handler.js and the node_modules folder it works, if I bundle with webpack and only zip the bundled file gives me a call exception error.

This is my webpack.config.js file (webpack 5.73):

const path = require("path");

module.exports = {
entry: path.resolve(__dirname, "index.js"),
output: {
path: path.resolve(__dirname, "dist"),
filename: "index.js",
libraryTarget: "commonjs2",
},
target: "node",
devtool: "inline-source-map",
};

Thanks in advance!

Code Snippet

const provider = new providers.InfuraProvider("homestead", projectId);
const erc = new Contract(contractAddress, abi, provider);

const amounts = await erc.balanceOfBatch(
  Array(tokens.length).fill(wallet), 
  tokens
);

Contract ABI

function balanceOfBatch(address[],uint256[]) view returns (uint256[])

Errors

missing revert data in call exception; Transaction reverted without a reason string [ See: https://links.ethers.org/v5-errors-CALL_EXCEPTION ]

Environment

node.js (v12 or newer)

Environment (Other)

No response

[ricmoo]

Can you include a console.log in your script running on AWS and include everything required to call it, such as the contract address, the list of tokens, etc. This is often a case of the parameters on the server not matching what you expect them to.

[ricmoo]

(moving to discussions for now, as there isn't currently enough detail to debug)

[Eikix]

I think this is linked with fetch not being available and the fact that somehow lambda is trying to access ethersjs as if it were a browser.
At least we have similar errors.