Hi guys, I am trying to create a discord bot using the discord.js library. Locally with

sst start

it works fine, but when I try to deploy it, it complains about an external module called ffmpeg-static. If I add this library to the externalModules property of the bundle, the deploy works, but my function does not work when I call the url, it complains about the following… (will put inside the thread). Does anybody have a clue of what might be happening? Thanks a lot in advance!

Hey @Manoel Feliciano, try using

nodeModules

instead of

externalModules

Will give it a try, thanks for the quick response Frank!

np! Modules listed in

externalModules

are excluded from the package. Where as with

nodeModules

, the modules are not bundled by esbuild, but included as in with the Lambda code.

When I do this, it asked me to install the library so it could be added in package.json.

you should see a

.build

folder in your app’s directory

Hmmm, I see. I will paste the cdk.out here.

oh i mean, can you show me an

ls

of what’s inside the

cdk.out

folder?

Sure.

So

asset.6624c5951b2e51ab2be1a1bac1fea422e47d1aa8c12a3820d4e8514b464eeccd

is the packaged Lambda code. Can you do an

ls

in there?

Here it goes:

total 4088
drwxr-xr-x   7 manoelfeliciano  staff      224  5 Jul 18:55 .
drwxr-xr-x   8 manoelfeliciano  staff      256  5 Jul 18:55 ..
-rw-r--r--   1 manoelfeliciano  staff   776985  5 Jul 18:55 lambda.js
-rw-r--r--   1 manoelfeliciano  staff  1298513  5 Jul 18:55 lambda.js.map
drwxr-xr-x  26 manoelfeliciano  staff      832  5 Jul 18:55 node_modules
-rw-r--r--   1 manoelfeliciano  staff       44  5 Jul 18:55 package.json
-rw-r--r--   1 manoelfeliciano  staff     6655  5 Jul 18:55 yarn.lock

right, and since u have

nodeModules

configured,

ffmpeg-static

should be packaged separately into

node_modules

Yeah:

@derhuerst           core-util-is         inherits             readable-stream
@types               debug                isarray              safe-buffer
agent-base           env-paths            ms                   string_decoder
buffer-from          ffmpeg-static        parse-cache-control  typedarray
caseless             http-response-object process-nextick-args util-deprecate
concat-stream        https-proxy-agent    progress

hmm it’s there

Unfortunately, yes… But it works in

sst start

.

Which package is

AbortController

coming from?

Comes from a node_modules called abort-controller. Which is quite interesting, after adding it locally to package.json and additing to that node_modules property the error is gone. But I get another one:

{
  "errorType": "Runtime.UnhandledPromiseRejection",
  "errorMessage": "TypeError: fetch is not a function",
  "reason": {
    "errorType": "TypeError",
    "errorMessage": "fetch is not a function",
    "code": 500,
    "name": "TypeError",
    "method": "get",
    "path": "/gateway/bot",
    "stack": [
      "TypeError: fetch is not a function",
      "    at RequestHandler.execute (/var/task/lambda.js:12049:17)",
      "    at RequestHandler.execute (/var/task/lambda.js:12052:21)",
      "    at RequestHandler.push (/var/task/lambda.js:12015:27)",
      "    at async WebSocketManager2.connect (/var/task/lambda.js:23592:11)",
      "    at async Client.login (/var/task/lambda.js:24269:9)"
    ]
  },
  "promise": {},
  "stack": [
    "Runtime.UnhandledPromiseRejection: TypeError: fetch is not a function",
    "    at process.<anonymous> (/var/runtime/index.js:35:15)",
    "    at process.emit (events.js:314:20)",
    "    at processPromiseRejections (internal/process/promises.js:209:33)",
    "    at processTicksAndRejections (internal/process/task_queues.js:98:32)"
  ]
}

hmm.. can I see your package.json and ur lambda code?

Sure. Thanks a lot for the help in advance!

Thanks @Manoel Feliciano for sharing it!