I have a serverless functions i use it with hasura actions. Work fine in local. But i got this deploy error. I have no installed packages such as "mock-aws-s3".

couldn't build lambda for /tmp/1693465139/functions/insert-user-password.ts: ✘ [ERROR] Could not resolve "mock-aws-s3" nodemodules/@mapbox/node-pre-gyp/lib/util/s3setup.js:43:28: 43 │ const AWSMock = require('mock-aws-s3'); ╵ ~~~~~~~~~~~~~ You can mark the path "mock-aws-s3" as external to exclude it from the bundle, which will remove this error. You can also surround this "require" call with a try/catch block to handle this failure at run-time instead of bundle-time. ✘ [ERROR] Could not resolve "aws-sdk" nodemodules/@mapbox/node-pre-gyp/lib/util/s3setup.js:76:22: 76 │ const AWS = require('aws-sdk'); ╵ ~~~~~~~~~ You can mark the path "aws-sdk" as external to exclude it from the bundle, which will remove this error. You can also surround this "require" call with a try/catch block to handle this failure at run-time instead of bundle-time. ✘ [ERROR] Could not resolve "nock" nodemodules/@mapbox/node-pre-gyp/lib/util/s3setup.js:112:23: 112 │ const nock = require('nock'); ╵ ~~~~~~ You can mark the path "nock" as external to exclude it from the bundle, which will remove this error. You can also surround this "require" call with a try/catch block to handle this failure at run-time instead of bundle-time. 3 errors

@emrneo Would you mind sharing your package.json here?

{
"name": "functions",
"version": "1.0.0",
"description": ""
"main": "index.js",
"devDependencies": {
"@types/bcrypt": "^5.0.0"
},
"scripts": {
"test": "echo \"Error: no test specified\" && exit 1"
},
"keywords": [],
"author": "",
"license": "ISC",
"dependencies": {
"@types/express": "^4.17.14",
"bcrypt": "^5.1.0",
"node-fetch": "^3.2.10"
}
}

@elitan

Sorry, nothing stands out from this package.json

Are you able to publicly post the serverless function code?

Looks to be related to mapbox?

and I don't understand why. You don't have a lot of packages in your package.json

Works fine in local

Can you try using bcryptjs instead of bcrypt. I think bcrypts uses a binary and we have issues with that in our infra atm. Similar to this: https://github.com/nhost/nhost/issues/933

bcryptjs: https://www.npmjs.com/package/bcryptjs

I ran into this issue recently as well. Switching from pnpm to yarn to manage my packages made it work.

@TaylorFay Altough i use yarn i had this issue. Maybe some c++ codes of bcrypt conflict with nhost infra.