deno.land being inaccessible breaks application

[ghost]

For some reason, deno.land being down breaks my application; this is a big problem.

error: Uncaught CompileError: WebAssembly.Module(): expected magic word 00 61 73 6d, found 35 30 30 3a @+0
  wasm_mod = new WebAssembly.Module(await ('file:' === path.protocol ? Deno.readFile(path) : fetch(path).then(r => r.arrayBuffer())));
             ^
    at https://deno.land/x/imagescript@1.2.15/utils/wasm/png.js:6:14
    at eventLoopTick (ext:core/01_core.js:181:11)

The import that triggers this:

import {decode, Image} from "https://deno.land/x/imagescript@1.2.15/mod.ts";

When I visit https://deno.land/x/imagescript@1.2.15/utils/wasm/png.js, I get a 500 error:

How can I prevent this from being a problem in the future?

[sigmaSd]

Its a remote import so the server failing will always be show stopper, so I think the only to prevent this is to vendor your dependencies

[bradenmacdonald]

If you use a dependency that requires WebAssembly/wasm code, Deno does not "know" about the wasm file import and needs to fetch it over the internet every time. Follow the issue #2552 to know when wasm imports have been implemented in Deno. Once that has been implemented, you could get your dependencies updated to use the new import method, and this problem should go away.

Until then, the only other option as pointed out is to have a full local ("vendored") copy of your dependency including its wasm module files.

[lucacasonato]

#2552