Michele
01/13/2022, 3:22 PM{
"errorType": "Runtime.UserCodeSyntaxError",
"errorMessage": "SyntaxError: Unexpected token 'export'",
"stack": [
"Runtime.UserCodeSyntaxError: SyntaxError: Unexpected token 'export'",
" at _loadUserApp (/var/runtime/UserFunction.js:98:13)",
" at Object.module.exports.load (/var/runtime/UserFunction.js:140:17)",
" at Object.<anonymous> (/var/runtime/index.js:43:30)",
" at Module._compile (internal/modules/cjs/loader.js:999:30)",
" at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)",
" at Module.load (internal/modules/cjs/loader.js:863:32)",
" at Function.Module._load (internal/modules/cjs/loader.js:708:14)",
" at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:60:12)",
" at internal/main/run_main_module.js:17:47"
]
}
This burst of errors is limited to a 15 min timespan, before & after the logs are are fine with no other issues reported.
We’re not making any use of the /api
routes in the NextJS project so we don’t need any support for its “backend”.
Would you have any tip on how to troubleshoot this issue?
Thank you in advance!Michele
01/13/2022, 3:24 PMexport async function handler() {
// placeholder function
}
Frank
Frank
Frank
Michele
01/28/2022, 3:49 PM@serverless-stack-slack/cli
and @serverless-stack/resources
version in the package.json file? I tried running npm update @serverless-stack/cli @serverless-stack/resources
but this only updates the package-lock.json, the version for those packages stays at our current one (v0.53.2) in package.json.
Apologies for the naive question, not too knowledgeable in this topic 😅Frank
sst update
command, ie. npx sst update 0.60.5
. With the exception that if you are currently on a version earlier than 0.59.0
, you’d have to follow these steps to update to 0.59.0
first.Michele
01/30/2022, 10:02 PM