For the versioning thing: each of those would presumably pull from a different url, so they’d be fully independent. That might result in redundant downloads, bu

For the versioning thing: each of those would presumably pull from a different url, so they’d be fully independent. That might result in redundant downloads, but that should be fine, because we’re not talking about the front-end. Deno has no knowledge of versions, just urls. The permissions model may have been a mistake. In my own projects I find myself just doing —-allow-all constantly. I could see it being useful for a hardened production server that eg. should only have access to the network, but I think permission-denial may have been better than permission-granting. Maybe they’ll change the CLI around this at some point.