Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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 @gustavogarcete,
It seems like with NODE_ENV=production Yarn will skip installing some packages that are actually required for the build, usually those configured as devDependencies.
What you can do is set the NODE_ENV variable only at run-time, like so:
...
services:
- ...
envs:
- key: NODE_ENV
scope: RUN_TIME
value: production
...
This way the build will continue as usual and your app will run with NODE_ENV set to production.