-
-
Notifications
You must be signed in to change notification settings - Fork 793
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
Why serverless offline says found unsupported runtime nodejs8.10? #381
Comments
It needs an update: serverless-offline/src/index.js Line 318 in 4162446
13 PRS and repos owners profile says hes on vacation till 2018. Thanks @cmendes0101 :D I've made a PR |
I know this issue is closed, but if it does a |
I would agree that it should throw an |
I am running into this right now — as @clschnei mentioned I am node 8.10 locally (via nvm use 8.10) but I am getting the following error: Have upgraded Serverless and Serverless-Offline. For what it's worth my serverless.yml runtime is set to:
|
OK so I copied my node_modules directory over from a pre-existing project on the same stack and now it works. My guess it is some combination of the serverless version, serverless offline version and potentially serverless offline sqs versions. Since I am on a paid client gig I can't go further into it than that — but obviously this was not a Runtime issue in my case as well, and the Warning text cost me time when trouble shooting. |
Sorry to hijack this thread, but I'm getting a similar error in a go lang project, scaffolded with:
I'm running this command:
and getting this output:
I get this fine output when the lambda function loads up:
But then when I try to hit the endpoint it crashes with this error:
|
Hi @JimLynchCodes, do you able to solve the problem given above? |
Did you found any solution for the above one? |
This might be an old thread but I ended up here after getting the error described by @JimLynchCodes. For future references, Go runtime is supported only via
|
The text was updated successfully, but these errors were encountered: