-
-
Notifications
You must be signed in to change notification settings - Fork 794
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Block-scoped declarations (let, const, function, class) not yet supported outside strict mode #183
Comments
Damn this is my fault. Thanks @paulSambolin, will fix now. |
@dherault No problem! Thanks for the quick response |
v3.8.1 should fix it. |
I'm currently getting an error only when serverless v3.8.1 is enabled in plugins (node 4.6, sls 1.3) SyntaxError: Unexpected token ...
at exports.runInThisContext (vm.js:53:16)
at Module._compile (module.js:373:25)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at /usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:59:22
at Array.forEach (native)
at PluginManager.loadPlugins (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:58:13)
at PluginManager.loadServicePlugins (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:86:10)
at PluginManager.loadAllPlugins (/usr/local/lib/node_modules/serverless/lib/classes/PluginManager.js:54:10)
at /usr/local/lib/node_modules/serverless/lib/Serverless.js:64:28``` |
On it @LoxyFox |
v3.8.2 |
@dherault did the trick. Thanks! |
This was referenced Jun 20, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Sorry this post might not have alot of information, we are deploying via AWS codebuild, so the output is a little fragmented.
The error was thrown when serverless was attempting to load Plugins. I came to my conclusion by commenting out the serverless-offline plugin and re-running the deployment. It worked, and this just began recently (newest version??).
I looked through the most recent commits and couldn't find the issue, it is most likely a missing 'use strict` tag
The text was updated successfully, but these errors were encountered: