Getting error "Supplied code must return or export a function." on new deployments
See original GitHub issueTeam, I recently started getting the error in runtime
{
"code": 400,
"message": "Invalid webtask code",
"error": "Supplied code must return or export a function."
}
when I invoke the webtask. The webtask duly has the structure
const webtaskApi = module.webtask;
module.exports = function(e) {
}
What could be wrong?
Issue Analytics
- State:
- Created 5 years ago
- Comments:17 (9 by maintainers)
Top Results From Across the Web
Troubleshoot deployment issues in Lambda
Deployment errors prevent the new version from being used and can arise from issues with your deployment package, code, permissions, or tools.
Read more >Troubleshoot common Azure deployment errors
Error code Mitigation More inform...
AccountNameInvalid Follow naming guidelines for storage accounts. Resolve erro...
AccountPropertyCannotBeSet Check available storage account properties. storageAcco...
AnotherOperationInProgress Wait for concurrent operation...
Read more >Troubleshooting Cloud Functions - Google Cloud
Cloud Functions deployment can fail if the entry point to your code, that is, the exported function name, is not specified correctly. The...
Read more >Errors – Vercel Docs
A list of errors provided by Vercel CLI or the REST API, with details on how they occur and how to resolve them....
Read more >Getting Unexpected Token Export - javascript - Stack Overflow
there is not enough information about your environment or configuration to offer any assistance. This error is suggesting that either webpack or babel...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks a bunch!!
@baskin
This issue should now be resolved with the release of wt-cli v11.0.0.