3 ms·
Deno should have like a mirrors.manifest.js file that stores your dependency links, and mirrors, should one source go down... that way it wouldn't be such a pro
by gremlinsinc 4y ago
Deno should have like a mirrors.manifest.js file that stores your dependency links, and mirrors, should one source go down... that way it wouldn't be such a problem, the only big issue might be ensuring the sources don't have a rogue link or two from bad actors, where they do something nefarious like build a useful package then swap it out for a bad version later on, and put only on a mirror so when things go south it triggers, of course there could be bots/queues that periodically take md5s of the code, or just whenever version changes occur, so that would stop that.
- crdrost 4y agoThis exists and is part of the deno executable; see [1] for more info. 1. https://deno.land/manual@v1.31.1/tools/vendor https://deno.land/manual@v1.31.1/tools/vendor
- qbasic_forever 4y agoDeno puts a hash of the dependency contents in a lock file so it can ensure the contents of a dependency haven't been changed unexpectedly: https://deno.land/manual@v1.29.2/basics/modules/integrity_checking https://deno.land/manual@v1.29.2/basics/modules/integrity_ch...