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
gefragt vor einem Jahr1248 Aufrufe
2 Antworten
1
Akzeptierte Antwort

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

Rick
beantwortet vor einem Jahr
profile pictureAWS
EXPERTE
überprüft vor einem Jahr
0

Hi Rick,

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

profile pictureAWS
EXPERTE
beantwortet vor einem Jahr
  • 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. :)

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen