News for hackers. Stuff that matters.

A comment on Deno 1.0. Parent comment

Re:Deno 1.0 by xg15 on Wednesday May 13, 2020 @07:52PM (#23173307)
How would this work with transitive dependencies? Sure I can control which parts I import myself, but how do I keep a vendored file from pulling in another URL a level deeper?
[ Parent | on HN ]
Re:Deno 1.0 by thebradbain on Wednesday May 13, 2020 @07:57PM (#23173345)
Unlike node, recommended deno practice is to check-in your dependencies to the VCS.

> Production software should always bundle its dependencies. In Deno this is done by checking the $DENO_DIR into your source control system, and specifying that path as the $DENO_DIR environmental variable at runtime.

https://deno.land/manual/linking_to_external_code

[ Parent | on HN ]
Re:Deno 1.0 by Rotareti on Thursday May 14, 2020 @06:06AM (#23177630) 

    du -hs node_modules
    
    1.7G node_modules
[ Parent | on HN ]