5 ms·

Unless I'm massively misunderstanding your setup, that Docker image contains an entire OS and runtime, not just your website. Reasonable people can disagree abo

Unless I'm massively misunderstanding your setup, that Docker image contains an entire OS and runtime, not just your website. Reasonable people can disagree about whether that entire paradigm is sensible but, having chosen to use Docker, complaining about image size in this way seems an odd choice. More to this point, most of what is in the image will be little to do with Node or its build systems..

toomanybeersies 4y ago
The NodeJS alpine base image is only 40 MB.
- lolive 4y ago
  Then you _npm install_ something, and BOOOM! 600MB !
  - Defman 4y ago
    You can use multi-stage builds [1] so your result image would be as small as possible by just copying the compiled JS from the build stage. [1]: https://docs.docker.com/develop/develop-images/multistage-build/ https://docs.docker.com/develop/develop-images/multistage-bu...
    - hinkley 4y ago
      Compiled JavaScript?
      - veyh 4y ago
        Bundled. With esbuild, for example.
      - Defman 4y ago
        My bad, I meant "bundled".
    - vbezhenar 4y ago
      You still need to download hundreds of megabytes of packages, unpack those into gigabyte of storage, "compile" it into a final form. Also you need to keep those huge images, if you want to have any reasonable caching. Otherwise builds will take forever.