-
-
Notifications
You must be signed in to change notification settings - Fork 24
Error: when using the layer in Node v18 #13
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
Comments
I have the same error |
This was a mistake on my end, I can't replicate this error |
@DavidVaness I found the build script should move the node_modules folder to either node16 or node18 and ensure there should be no /opt/nodejs/node_modules folder, still have to fix it. May I know if you could run your Lambda function or not at the moment? |
I am sorry, I have this error on node18, must have been some caching issue that lead me to assume the 18 works while receiving data from the working v16 And the error message supports your path to fix the issue, as he is unable to link the files
|
@DavidVaness, @stuharben, The maintenance release v2.11.1 of the canvas layer has just been updated on serverless repo, could you please try the latest release? You may deploy the latest layer through the serverless repo or upload the latest release from the Releases section. Please let me know if the release works stable at your side or not. Thank you. |
Hi @charoitel - thank you for this work. Really helped me out.
We built the layer using your AWS serverless application. It works fine in v16, though when using as a layer in Node v18 we get intermittent errors:
We also used Cloud9 to step through your code and run it just for Node v18 and it gives a similar error:
Thank you so much in advance!
The text was updated successfully, but these errors were encountered: