Lazily construct wasm module about deno_graph

[dsherret]

@kitsonk in ts-morph I'm planning to use it and it would only get called if someone analyzes deno code (ex. for node code it wouldn't be necessary).

[kitsonk]

Thanks that makes sense. Also, TLA can actually be a challenge with things like Deploy when trying to instantiate the isolate. Having a constructor does make sense.

The pattern here works well (which was adapted from other projects as well):

https://github.com/lucacasonato/comrak-wasm/blob/a8b06e882c43c06de1d1a48e894b6c4f1c0de921/mod.ts#L10-L18

I also do like the init() versus load()...

[kitsonk]

I agree with the first point, but:

deno graph is imported but not used

😕 why would someone do that. What valid scenarios are there for that?

[dsherret]

The one thing I like about load vs init is that load forces you to call it in order to use the API, whereas init doesn't and I'm not sure how friendly the error message is if you forget to (or at least we'd have to implement something). I can implement init though.

[dsherret]

This is done now in #158.