Trick the webpack to bypass its warnings on missing modules

[fzhinkin]

Leftovers from #265

[whyoleg]

LGTM
But, is there a reason why Wasm and JS implementations are different?
In my experiments current approach works for both Wasm and JS, and so the implementation looks similar (except for minor differences in jsinterop for wasm vs js), so it's easier to understand the code and so could mostly copy-pasted

[fzhinkin]

But, is there a reason why Wasm and JS implementations are different?

There was a reason, but now it seems like it should be possible to unify it.

[fzhinkin]

Filed #287 for unifying module loading

[lppedd]

I've missed the discussion about this change. Why couldn't Webpack simply be configured to mute those warnings?

E.g., configure externals, or use the ignore plugin.

[fzhinkin]

@lppedd If I understand correctly, it could be done on the library user side only, which is kinda lame. Instead, the root cause of the warning was fixed (well, not fixed, but muted).

[lppedd]

@fzhinkin Thanks. I get that not displaying a warning consumer side is nice, but isn't it better to make the consumer aware of what is going on instead of hiding it? I mean, once I start working with K/JS I know that Webpack runs for browser, so I can fiddle with its configuration in case. This could be highlighted in the readme.