wasm-bindgen/examples/wasm-in-wasm/Cargo.toml

[package]
name = "wasm-in-wasm"
version = "0.1.0"
authors = ["The wasm-bindgen Developers"]

[lib]
crate-type = ["cdylib"]

[dependencies]
wasm-bindgen = "0.2.27"
js-sys = "0.3.4"
Add an example of namespaced APIs By creating wasm modules from Rust! 2018-03-22 17:39:48 -07:00			`[package]`
			`name = "wasm-in-wasm"`
			`version = "0.1.0"`
Don't use path dependencies in examples This commit updates all examples to not use `path` dependencies but rather use versioned dependencies like would typically be found in the wild. This should hopefully make the examples more copy-pastable and less alien to onlookers! The development of the examples remains the same where they continue to use the `wasm-bindgen`, `js-sys`, `web-sys`, etc from in-tree. The workspace-level `[patch]` section ensures that they use the in-tree versions instead of the crates.io versions. 2018-11-07 11:14:25 -08:00			`authors = ["The wasm-bindgen Developers"]`
Add an example of namespaced APIs By creating wasm modules from Rust! 2018-03-22 17:39:48 -07:00
			`[lib]`
			`crate-type = ["cdylib"]`

			`[dependencies]`
Don't use path dependencies in examples This commit updates all examples to not use `path` dependencies but rather use versioned dependencies like would typically be found in the wild. This should hopefully make the examples more copy-pastable and less alien to onlookers! The development of the examples remains the same where they continue to use the `wasm-bindgen`, `js-sys`, `web-sys`, etc from in-tree. The workspace-level `[patch]` section ensures that they use the in-tree versions instead of the crates.io versions. 2018-11-07 11:14:25 -08:00			`wasm-bindgen = "0.2.27"`
			`js-sys = "0.3.4"`