wasm-bindgen/crates/wasm-bindgen-cli-support/Cargo.toml

[package]
name = "wasm-bindgen-cli-support"
version = "0.1.0"
authors = ["Alex Crichton <alex@alexcrichton.com>"]

[dependencies]
parity-wasm = "0.23"
failure = "0.1"
wasm-bindgen-shared = { path = "../wasm-bindgen-shared" }
serde_json = "1.0"
base64 = "0.9"
Initial commit 2017-12-14 19:31:01 -08:00			`[package]`
			`name = "wasm-bindgen-cli-support"`
			`version = "0.1.0"`
			`authors = ["Alex Crichton <alex@alexcrichton.com>"]`

			`[dependencies]`
Update parity-wasm dependency 2018-01-25 13:32:27 -08:00			`parity-wasm = "0.23"`
Initial commit 2017-12-14 19:31:01 -08:00			`failure = "0.1"`
			`wasm-bindgen-shared = { path = "../wasm-bindgen-shared" }`
			`serde_json = "1.0"`
Rewrite wasm-bindgen with ES6 modules in mind This commit is a mostly-rewrite of the `wasm-bindgen` tool. After some recent discussions it's clear that the previous model wasn't quite going to cut it, and this iteration is one which primarily embraces ES6 modules and the idea that this is a polyfill for host bindings. The overall interface and functionality hasn't changed much but the underlying technology has now changed significantly. Previously `wasm-bindgen` would emit a JS file that acted as an ES6 module but had a bit of a wonky interface. It exposed an async function for instantiation of the wasm module, but that's the bundler's job, not ours! Instead this iteration views each input and output as a discrete ES6 module. The input wasm file is interpreted as "this should be an ES6 module with rich types" and the output is "well here's some ES6 modules that fulfill that contract". Notably the tool now replaces the original wasm ES6 module with a JS ES6 module that has the "rich interface". Additionally a second ES6 module is emitted (the actual wasm file) which imports and exports to the original ES6 module. This strategy is hoped to be much more amenable to bundlers and controlling how the wasm itself is instantiated. The emitted files files purely assume ES6 modules and should be able to work as-is once ES6 module integration for wasm is completed. Note that there aren't a ton of tools to pretend a wasm module is an ES6 module at the moment but those should be coming soon! In the meantime a local `wasm2es6js` hack was added to help make something work today. The README has also been updated with instructions for interacting with this model. 2018-01-29 21:20:38 -08:00			`base64 = "0.9"`