I want to run a simple nodeJS script as a function in DO Functions. But the nodeJS requires one or more dependencies which need to be stored in node_modules. How do we run a nodeJS script that way ? I mean, we would need to upload a package.json and run npm i right before we can execute that script as a function in DO ?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi there,
You can still have your dependencies defined in a
package.json
file as normal. The platform will detect the file and will install those dependencies as normal.You don’t have to commit the
node_modules
directory.Here is an example of a Node App with a
package.json
file:The README md file contains the instructions on how to deploy that sample Node function.
Let me know if you have any questions!
Best,
Bobby
Thats a big lie cause I say which dependency Im gonna use in package.json and function still says “canot find node modules”
Have you added the
package.json
inside the function directory? Is your function open-source, if so feel free to share the link to the GitHub repo so I can take a look.I’ve gotten a similar problem, but it can’t find
npm
:thinking:, more info here: https://www.digitalocean.com/community/questions/followed-all-info-i-could-find-getting-npm-command-not-foundHi there,
I’ve just replied to your question. The error that you are using is not that
npm
is missing but that it is failing to install your packages for some reason.This worked for me; however it seems like a few of my dependencies are causing a large a deployment.zip and I am unable to deploy the function using the
doctl
CLI.I’m getting a
413 payload too large
Are there any recommended solutions to avoiding this? I’ve ran into similar issues with AWS Lambda – the workaround was to construct the deployment zip, upload it to S3, and then deploy the function by referencing the S3 path.