You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I wonder about the technical reasons behind the limited node v8 support.
You've stated in the readme that only versions >=8.12.0 are supported by Hapi v18.x, why is that?
I'm concerned because the package serverless-offline has upgraded to hapi v18 in their latest version, but AWS Lambda (one of the possible aws official node engine alongside v10.x) only supports v8.10.
Hence, I'm wondering what are the technical limitations node v8.10 has that makes it incompatible with hapi.
We just use the latest version because that's the only one we test. If you use other versions, you should probably test it by running all the hapi tests.
This thread has been automatically locked due to inactivity. Please open a new issue for related bugs or questions following the new issue template instructions.
lockbot
locked as resolved and limited conversation to collaborators
Jan 9, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
supportQuestions, discussions, and general support
I wonder about the technical reasons behind the limited node v8 support.
You've stated in the readme that only versions >=8.12.0 are supported by Hapi v18.x, why is that?
I'm concerned because the package
serverless-offline
has upgraded to hapi v18 in their latest version, but AWS Lambda (one of the possible aws official node engine alongside v10.x) only supports v8.10.Hence, I'm wondering what are the technical limitations node v8.10 has that makes it incompatible with hapi.
See dherault/serverless-offline#741
The text was updated successfully, but these errors were encountered: