Re:Deno 1.0
by afiori on Wednesday May 13, 2020 @07:44PM
(#23173247)
Deno caches local copies and offer control on when to reload them. in term of vendoring you can simply download everything yourself and use local paths for imports.
[ Parent
| on HN ]
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?
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.
du -hs node_modules
1.7G node_modules> in term of vendoring you can simply download everything yourself and use local paths for imports.
So I basically have to do manually, what NPM/yarn do for me already?
I do not speak for the project, but based on my understanding part of the point was to avoid the magic of npm.
You can use lock-files, bundles, and many other features that makes dependencies management easier.
Ah from that perspective I can see how this might appear to be better. Personally, I like the 'magic' of NPM (which to be honest I don't really think is all that magical, it's quite transparent what's happening behind the scenes). This 'magic' means I no longer have to write 200 line makefiles, so it definitely makes my life easier.