Add more JS initialization options about wasm-bindgen HOT 8 CLOSED

I'd definitely be on board with this! I like the idea of "given the set of nice imports give me a set of low-level imports" as well as the reverse for the exports. Would you be interested in trying your hand at adding these?

from wasm-bindgen.

Great, thanks for the quick response! Yes, I'd be happy to give it a try. It looks like the key file is crates/wasm-bindgen-cli-support/src/ts.rs. Any parallel spots I should look for?

from wasm-bindgen.

Nah yeah that's it! The file isn't exactly the cleanest of files, but you can see the template down at the bottom

from wasm-bindgen.

@TimHambourger ah so actually, you may wish to hold off! I was having some discussion today with others and actually I think the current approach to the wasm module isn't quite right. I think we'll want to generate wasm/js files differently to better respect ES6 module integration with wasm.

I'll try to update this repo soon!

from wasm-bindgen.

As a general overview though what I'd hope to do is to actually generate a JS file file that starts with something like:

import * as wasm from './low-level.wasm';

in the sense that the instantiation of the wasm module would largely be up to the bundler rather than this library.

from wasm-bindgen.

Ok! I've rewritten the bindgen tool at the es6-modules branch -- https://github.com/alexcrichton/wasm-bindgen/tree/es6-modules, with some notable info in the commit message.

@TimHambourger mind giving that a spin and see if it works for you?

from wasm-bindgen.

Ah ok I went ahead and merged to master so this should be fixed now!

from wasm-bindgen.

@alexcrichton You move fast! Thanks for the updates and sorry to take a couple days to get back.

I definitely appreciate the desire to move instantiation out of this library. I've seen other tools that take a wasm-as-module approach, e.g. wasm-loader for webpack. I like the concept - treat wasm like just another code asset. It seems like the trade-off is less control over how/when the wasm gets compiled and instantiated. Or at least, the existing bundlers I've seen don't seem to give that kind of control. I'm also seeing different APIs from the different bundlers. E.g. wasm-loader exports a different API than your wasm2es6js. So there's some danger of becoming dependent on a particular bundler.

But those questions aside, the latest code is working great otherwise. So I'm happy leaving this one closed. And I'm excited to see where the library goes from here. All cool stuff!

from wasm-bindgen.