Lambda Node18 type module, extension .mjs, results in ES error loading module

0

So, my package.json has type:module and the handler file extension is .mjs, so why am I getting this error?

ERROR (node:8) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.

followed by this one:

2023-06-27T13:49:12.742Z undefined ERROR Uncaught Exception { "errorType": "Runtime.UserCodeSyntaxError", "errorMessage": "SyntaxError: Unexpected token 'export'", "stack": [ "Runtime.UserCodeSyntaxError: SyntaxError: Unexpected token 'export'", " at _loadUserApp (file:///var/runtime/index.mjs:994:17)", " at async UserFunction.js.module.exports.load (file:///var/runtime/index.mjs:1032:21)", " at async start (file:///var/runtime/index.mjs:1195:23)", " at async file:///var/runtime/index.mjs:1201:1" ] }

Rick
已提問 1 年前檢視次數 1250 次
2 個答案
1
已接受的答案

It turned out that my serverless.yml deployment file was excluding the package.json file. Resolved.

Rick
已回答 1 年前
profile pictureAWS
專家
已審閱 1 年前
0

Hi Rick,

Please take a look at this re:Post and see if it helps.

profile pictureAWS
專家
已回答 1 年前
  • Thanks, but not helpful, kinda the opposite of my error (as it knows type=module), but thanks anyway.

  • Checking further, as I remember that I have faced something similar. Hold on. :)

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南