3 ms·
Unless I'm missing something, does the lack of an 'install' command (be it for non-npm or npm libraries so you can bundle the packages with your image) not mean
by Piegie 4y ago
Unless I'm missing something, does the lack of an 'install' command (be it for non-npm or npm libraries so you can bundle the packages with your image) not mean it's detrimental to any deployment where you have either horizontal scaling or cold starts (eg. GCP Cloud Run)?
- deleted 4y ago[deleted]
- Piegie 4y agoAh, there is this: https://deno.land/manual@v1.28.0/advanced/continuous_integration#caching-dependencies https://deno.land/manual@v1.28.0/advanced/continuous_integra..., however I can't seen to find any specific page for a 'deno cache' CLI command aside from some loosely related pages that use the command.
- dsherret 4y agoThe `deno cache` command (ex. `deno cache main.ts` or `deno cache --node-modules-dir main.ts` if you want a node_modules folder) will ensure all npm packages used in the provided module are cached ahead of time. It acts similarly to a `npm install` if you need it. Also, at the moment, npm specifiers aren't supported with `deno compile` (https://deno.land/manual@v1.28.0/tools/compiler https://deno.land/manual@v1.28.0/tools/compiler), but in the future that will be one way to have a self contained executable with everything ready to go.
- simlevesque 4y agoTo deploy you'd create a binary executable version of the whole project and deploy that. That's what Deno Deploy does, I think. This way the execution is almost garanteed to me the same and the edge network doesn't have to support the runtime at all, just allow binaries. https://deno.land/manual/tools/compiler https://deno.land/manual/tools/compiler