This refactors out the dats.js file which handles the archiver into dat-registry-api. That means everything in this repo is now frontend or handling choo server side stuff. Woo.
With the update to the new dat-registry-api version, it will check to make sure the dat is available and cache it's metadata before confirming the publish. If the url is unreachable or the dat isn't available, it'll fail.
This refactors out the dats.js file which handles the archiver into dat-registry-api. That means everything in this repo is now frontend or handling choo server side stuff. Woo.
With the update to the new dat-registry-api version, it will check to make sure the dat is available and cache it's metadata before confirming the publish. If the url is unreachable or the dat isn't available, it'll fail.