After my latest deployment I am getting the following error:
Jun 9, 11:16:42 AM: INIT_START Runtime Version: nodejs:16.v14 Runtime Version ARN: arn:aws:lambda:us-east-1::runtime:699b51cc1e44cad9b43e446b3b6f7e0834a78366955dc81cc7b459b0aa3f9175
Runtime.MalformedHandlerName: Bad handler
at _splitHandlerString (file:///var/runtime/index.mjs:900:15)
at Object.UserFunction.js.module.exports.load (file:///var/runtime/index.mjs:1031:36)
at start (file:///var/runtime/index.mjs:1195:42)
at ModuleJob.run (node:internal/modules/esm/module_job:193:25)
at async Promise.all (index 0)
at async ESMLoader.import (node:internal/modules/esm/loader:530:24)
at async loadESM (node:internal/process/esm_loader:91:5)
at async handleMainPromise (node:internal/modules/run_main:65:12)
However, I only did a minor change (changed a few numbers in an insignificant function).
This is happening for me now as well on a new site with React 18.2.0 and Next 13.4.4.
The site was working when deployed prior to today when I added Server Actions experimental. I have not yet removed that to test if it’s the root cause, but I wanted to mention it ASAP.
EDIT: I just redeployed the site and it seems to have fixed itself now. Multiple clear cache and deploys last night (around 1am EST) resulted in the error however. I’m suspecting some kind of transient error on the build servers?