rustwasm/wasm-bindgen
1
0
Fork 0
mirror of https://github.com/rustwasm/wasm-bindgen.git synced 2024-11-28 05:52:21 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity
9db0addb63
wasm-bindgen/Cargo.toml

94 lines
2.7 KiB
TOML
Raw Normal View History

Initial commit
2017-12-15 06:31:01 +03:00
[package]
name = "wasm-bindgen"
Bump to 0.2.29
2018-12-04 17:04:47 +03:00
version = "0.2.29"
Bump to 0.2.12 (#515) * Bump to 0.2.12 * Update all version numbers and deps * Update all listed authors to `["The wasm-bindgen Developers"]` * Update `repository` links to specific paths for each crate * Update `homepage` links to the online book * Update all links away from `alexcrichton/wasm-bindgen` * Add `#[doc]` directives for HTML URLs * Update more version requirements * Fill out CHANGELOG
2018-07-19 22:57:04 +03:00
authors = ["The wasm-bindgen Developers"]
Prep work for the 0.1 release
2018-03-06 07:24:35 +03:00
license = "MIT/Apache-2.0"
Add `links` section to `Cargo.toml` Because only a single `wasm_bindgen` version can be used in a dependency graph, pretend we link a native library so that `cargo` will provide better error messages than the esoteric linker errors we would otherwise trigger.
2018-08-30 21:22:48 +03:00
# Because only a single `wasm_bindgen` version can be used in a dependency
# graph, pretend we link a native library so that `cargo` will provide better
# error messages than the esoteric linker errors we would otherwise trigger.
links = "wasm_bindgen"
Prep work for the 0.1 release
2018-03-06 07:24:35 +03:00
readme = "README.md"
categories = ["wasm"]
Bump to 0.2.12 (#515) * Bump to 0.2.12 * Update all version numbers and deps * Update all listed authors to `["The wasm-bindgen Developers"]` * Update `repository` links to specific paths for each crate * Update `homepage` links to the online book * Update all links away from `alexcrichton/wasm-bindgen` * Add `#[doc]` directives for HTML URLs * Update more version requirements * Fill out CHANGELOG
2018-07-19 22:57:04 +03:00
repository = "https://github.com/rustwasm/wasm-bindgen"
homepage = "https://rustwasm.github.io/wasm-bindgen/"
Prep work for the 0.1 release
2018-03-06 07:24:35 +03:00
documentation = "https://docs.rs/wasm-bindgen"
description = """
Easy support for interacting between JS and Rust.
"""
Initial commit
2017-12-15 06:31:01 +03:00
Provide docs.rs metadata for generating docs Makes sure that docs.rs, when it supports it, provides all the documentation for all our features!
2018-09-05 22:57:36 +03:00
[package.metadata.docs.rs]
features = ['serde-serialize']
Disable test for lib/doctest, there are none!
2018-02-02 19:10:48 +03:00
[lib]
test = false
doctest = false
Work with `#![no_std]` contexts This commit adds support for both `#![no_std]` in the wasm-bindgen runtime support (disabled by default with an on-by-default `std` feature). This also adds support to work and compile in the context of `#![no_std]` crates. Closes #146
2018-04-19 23:08:54 +03:00
[features]
Move the `js` module to a `js_sys` crate (#512) * Move the `js` module to a `js_sys` crate * Update js-sys tests to pass again * Update binding_to_unimplemented_apis_doesnt_break_everything Remove its dependency on the `js` module * Update metadata for js-sys * Fix the `closures` example
2018-07-19 22:30:58 +03:00
default = ["spans", "std"]
Add `spans` feature to control `proc-macro2` Using `proc-macro2`'s `nightly` feature is a good default for most use cases. However, it causes a build error if used together with crates such as `cssparser` that also use `proc-macro2` from a build script. This change adds a default enabled feature `spans` that users can disable if they need to work around this conflict. Fixes #160.
2018-04-25 22:42:13 +03:00
spans = ["wasm-bindgen-macro/spans"]
Work with `#![no_std]` contexts This commit adds support for both `#![no_std]` in the wasm-bindgen runtime support (disabled by default with an on-by-default `std` feature). This also adds support to work and compile in the context of `#![no_std]` crates. Closes #146
2018-04-19 23:08:54 +03:00
std = []
Add JsValue::{from_serde, into_serde} These functions are activated with the `serde-serialization` feature of the `wasm-bindgen` crate. When activated they will allow passing any arbitrary value into JS that implements the `Serialize` trait and receiving any value from JS using the `Deserialize` trait. The interchange between JS and Rust is JSON. Closes #96
2018-04-27 05:03:46 +03:00
serde-serialize = ["serde", "serde_json", "std"]
Move the `unsize` feature behind a `nightly` Cargo feature This should fully stabilize the `wasm-bindgen` crate, preparing us for stable Rust!
2018-08-20 00:45:59 +03:00
nightly = []
Work with `#![no_std]` contexts This commit adds support for both `#![no_std]` in the wasm-bindgen runtime support (disabled by default with an on-by-default `std` feature). This also adds support to work and compile in the context of `#![no_std]` crates. Closes #146
2018-04-19 23:08:54 +03:00
Assert all attributes are used by default This commit implements a system that will assert that all `#[wasm_bindgen]` attributes are actually used during compilation. This should help ensure that we don't sneak in stray attributes that don't actually end up having any meaning, and hopefully make it a bit easier to learn `#[wasm_bindgen]`!
2018-11-28 02:14:59 +03:00
# Whether or not the `#[wasm_bindgen]` macro is strict and generates an error on
# all unused attributes
strict-macro = ["wasm-bindgen-macro/strict-macro"]
Add a feature for printing the macro's generated code (#212)
2018-05-26 02:17:54 +03:00
# This is only for debugging wasm-bindgen! No stability guarantees, so enable
# this at your own peril!
xxx_debug_only_print_generated_code = ["wasm-bindgen-macro/xxx_debug_only_print_generated_code"]
Initial commit
2017-12-15 06:31:01 +03:00
[dependencies]
Bump to 0.2.29
2018-12-04 17:04:47 +03:00
wasm-bindgen-macro = { path = "crates/macro", version = "=0.2.29" }
Add JsValue::{from_serde, into_serde} These functions are activated with the `serde-serialization` feature of the `wasm-bindgen` crate. When activated they will allow passing any arbitrary value into JS that implements the `Serialize` trait and receiving any value from JS using the `Deserialize` trait. The interchange between JS and Rust is JSON. Closes #96
2018-04-27 05:03:46 +03:00
serde = { version = "1.0", optional = true }
serde_json = { version = "1.0", optional = true }
Initial commit
2017-12-15 06:31:01 +03:00
Start migrating `wasm_bindgen` tests to `wasm_bindgen_test` (#602) This commit starts migrating the `wasm_bindgen` tests to the `wasm_bindgen_test` framework, starting to assemble the coffin for `wasm-bindgen-test-project-builder`. Over time all of the tests in `tests/all/*.rs` should be migrated to `wasm_bindgen_test`, although they may not all want to go into a monolithic test suite so we can continue to test for some more subtle situations with `#[wasm_bindgen]`. In the meantime those, the `tests/all/api.rs` tests can certainly migrate!
2018-08-01 22:19:19 +03:00
[target.'cfg(target_arch = "wasm32")'.dev-dependencies]
Bump to 0.2.29
2018-12-04 17:04:47 +03:00
js-sys = { path = 'crates/js-sys', version = '0.3.6' }
wasm-bindgen-test = { path = 'crates/test', version = '=0.2.29' }
Migrate the `serde-serialize` test to `wasm`
2018-08-06 19:43:55 +03:00
serde_derive = "1.0"
Bump to 0.2.18 At the same time, also add a `publish.rs` script to ease our publishing woes.
2018-08-27 23:25:38 +03:00
wasm-bindgen-test-crate-a = { path = 'tests/crates/a', version = '0.1' }
wasm-bindgen-test-crate-b = { path = 'tests/crates/b', version = '0.1' }
Start migrating `wasm_bindgen` tests to `wasm_bindgen_test` (#602) This commit starts migrating the `wasm_bindgen` tests to the `wasm_bindgen_test` framework, starting to assemble the coffin for `wasm-bindgen-test-project-builder`. Over time all of the tests in `tests/all/*.rs` should be migrated to `wasm_bindgen_test`, although they may not all want to go into a monolithic test suite so we can continue to test for some more subtle situations with `#[wasm_bindgen]`. In the meantime those, the `tests/all/api.rs` tests can certainly migrate!
2018-08-01 22:19:19 +03:00
Classes are now working!
2017-12-19 01:31:01 +03:00
[workspace]
Rewrite the README using Webpack Right now Webpack probably has the most mature support for loading wasm modules, so let's show off how to do that! Additionally this commits hello world as an example to the repository.
2018-03-03 07:11:30 +03:00
members = [
Rename directories to remove "wasm-bindgen-" prefix in sub-crates
2018-03-29 18:15:58 +03:00
"crates/cli",
Move the `js` module to a `js_sys` crate (#512) * Move the `js` module to a `js_sys` crate * Update js-sys tests to pass again * Update binding_to_unimplemented_apis_doesnt_break_everything Remove its dependency on the `js` module * Update metadata for js-sys * Fix the `closures` example
2018-07-19 22:30:58 +03:00
"crates/js-sys",
Add a test harness to directly execute wasm tests (#524) * Add a test harness to directly execute wasm tests This commits adds a few new crates and infrastructure to enable comands like: cargo test --target wasm32-unknown-unknown The intention here is to make it as low-friction as possible to write wasm tests and also have them execute in a reasonable amount of time. Eventually this is also hopefully enough support to do things like headless testing! For now though this is defintely MVP status rather than fully fleshed out. There's some more information at `crates/test/README.md` about how it works and how to use it, but for now this is mainly intended to play around with locally in this repository for our own tests. * Port a numbe of `js-sys` tests to the new test framework This commit ports a number of existing tests for the `js-sys` crate over to the new test framework created in the previous commit, showing off how they can be executed as well as drastictlly simplifying the tests themselves! This is intended to be a proof of concept for now which we can refine over time. This should also show off that it's possible to incrementally move over to the new test framework.
2018-07-20 21:47:49 +03:00
"crates/test",
Support asynchronous tests (#600) * Tweak the implementation of heap closures This commit updates the implementation of the `Closure` type to internally store an `Rc` and be suitable for dropping a `Closure` during the execution of the closure. This is currently needed for promises but may be generally useful as well! * Support asynchronous tests This commit adds support for executing tests asynchronously. This is modeled by tests returning a `Future` instead of simply executing inline, and is signified with `#[wasm_bindgen_test(async)]`. Support for this is added through a new `wasm-bindgen-futures` crate which is a binding between the `futures` crate and JS `Promise` objects. Lots more details can be found in the details of the commit, but one of the end results is that the `web-sys` tests are now entirely contained in the same test suite and don't need `npm install` to be run to execute them! * Review tweaks * Add some bindings for `Function.call` to `js_sys` Name them `call0`, `call1`, `call2`, ... for the number of arguments being passed. * Use oneshots channels with `JsFuture` It did indeed clean up the implementation!
2018-08-01 23:52:24 +03:00
"crates/test/sample",
Add prototype of wasm-bindgen-typescript
2018-06-04 22:44:47 +03:00
"crates/typescript",
Prepare to have targeted error diagnostics (#604) This commit starts to add infrastructure for targeted diagnostics in the `#[wasm_bindgen]` attribute, intended eventually at providing much better errors as they'll be pointing to exactly the code in question rather than always to a `#[wasm_bindgen]` attribute. The general changes are are: * A new `Diagnostic` error type is added to the backend. A `Diagnostic` is created with a textual error or with a span, and it can also be created from a list of diagnostics. A `Diagnostic` implements `ToTokens` which emits a bunch of invocations of `compile_error!` that will cause rustc to later generate errors. * Fallible implementations of `ToTokens` have switched to using a new trait, `TryToTokens`, which returns a `Result` to use `?` with. * The `MacroParse` trait has changed to returning a `Result` to propagate errors upwards. * A new `ui-tests` crate was added which uses `compiletest_rs` to add UI tests. These UI tests will verify that our output improves over time and does not regress. This test suite is added to CI as a new builder as well. * No `Diagnostic` instances are created just yet, everything continues to panic and return `Ok`, with the one exception of the top-level invocations of `syn::parse` which now create a `Diagnostic` and pass it along. This commit does not immediately improve diagnostics but the intention is that it is laying the groundwork for improving diagnostics over time. It should ideally be much easier to contribute improved diagnostics after this commit! cc #601
2018-08-02 01:15:27 +03:00
"crates/macro/ui-tests",
Create the `web-sys` crate mechanically from WebIDL (#409) * Create a new `web-sys` crate This will eventually contain all the WebIDL-generated bindings to Web APIs. * ci: Test the new `web-sys` crate in CI * web-sys: Add a small README * web-sys: Vendor all the WebIDL files from mozilla-central * backend: Add a pass to remove AST items that use undefined imports This is necessary for the WebIDL frontend, which can't translate many WebIDL constructs into equivalent wasm-bindgen AST things yet. It lets us make incremental progress: we can generate bindings to methods we can support right now even though there might be methods on the same interface that we can't support yet. * webidl: Add a bunch of missing semicolons * webidl: Make parsing private It was only `pub` so that we could test it, but we ended up moving towards integration tests rather than unit tests that assert particular ASTs are parsed from WebIDL files. * webidl: Remove uses of undefined import types * test-project-builder: Build projects in "very verbose" mode This helps for debugging failing WebIDL-related tests. * test-project-builder: Add more profiling timers * test-project-builder: Detect when webpack-dev-server fails Instead of going into an infinite loop, detect when webpack-dev-server fails to start up and early exit the test. * webidl: Specify version for dev-dependency on wasm-bindgen-backend Instead of only a relative path. * guide: Add section about contributing to `web-sys` * WIP enable Event.webidl Still need to fix and finish the test. * Update expected webidl output * Start out a test's status as incomplete That way if we don't fill it in the error message doesn't look quite so bizarre * Fix onerror function in headless mode Otherwise we don't see any output! * Fix package.json/node_modules handling in project generation Make sure these are looked up in the git project root rather than the crate root * Avoid logging body text This was meant for debugging and is otherwise pretty noisy * Fix a relative path * More expected test fixes * Fix a typo * test-project-builder: Allow asynchronous tests * webidl: Convert [Unforgeable] attributes into `#[wasm_bindgen(structural)]` Fixes #432 * test-project-builder: Print generated WebIDL bindings for debugging purposes Helps debug bad WebIDL bindings generation inside tests. * When we can't find a descriptor, say which one can't be found This helps when debugging things that need to become structural. * web-sys: Test bindings for Event * ci: Use `--manifest-path dir` instead of `cd dir && ...` * web-sys: Just move .webidl files isntead of symlinking to enable them * tests: Polyfill Array.prototype.values for older browsers in CI * test-project-builder: Don't panic on poisoned headless test mutex We only use it to serialize headless tests so that we don't try to bind the port concurrently. Its OK to run another headless test if an earlier one panicked. * JsValue: Add {is,as}_{object,function} methods Allows dynamically casting values to `js::Object` and `js::Function`. * tidy: Fix whitespace and missing semicolons * Allow for dynamic feature detection of methods If we create bindings to a method that doesn't exist in this implementation, then it shouldn't fail until if/when we actually try and invoke that missing method. * tests: Do feature detection in Array.prototype.values test * Add JsValue::{is_string, as_js_string} methods And document all the cast/convert/check methods for js value. * eslint: allow backtick string literals * Only generate a fallback import function for non-structural imports
2018-07-10 02:35:25 +03:00
"crates/web-sys",
Move the `js` module to a `js_sys` crate (#512) * Move the `js` module to a `js_sys` crate * Update js-sys tests to pass again * Update binding_to_unimplemented_apis_doesnt_break_everything Remove its dependency on the `js` module * Update metadata for js-sys * Fix the `closures` example
2018-07-19 22:30:58 +03:00
"crates/webidl",
Migrate `webidl` tests to `wasm_bindgen_test` (#590) This commit moves the `webidl/tests` folder to a new `crates/webidl-tests` crate (to have a test-only build script) and ports them to the `#[wasm_bindgen_test]` attribute, which should hopefully make testing much speedier for execution!
2018-07-30 21:06:29 +03:00
"crates/webidl-tests",
chore: Sort workspace members
2018-07-25 23:44:14 +03:00
"examples/add",
example: Add an example of drawing a smiley face with canvas Adapted from https://developer.mozilla.org/en-US/docs/Web/API/Canvas_API/Tutorial/Drawing_shapes
2018-08-16 02:56:24 +03:00
"examples/canvas",
chore: Sort workspace members
2018-07-25 23:44:14 +03:00
"examples/char",
"examples/closures",
Add an example of console.log Also clean up some other exampels
2018-03-09 21:25:19 +03:00
"examples/console_log",
examples: Add an example of using duck-typed interfaces
2018-09-12 02:29:25 +03:00
"examples/duck-typed-interfaces",
Add an example of DOM access
2018-03-21 18:26:00 +03:00
"examples/dom",
Initial example for the Fetch API
2018-08-19 00:20:42 +03:00
"examples/fetch",
guide: Start adding example usage to "supported types" section
2018-08-11 02:56:40 +03:00
"examples/guide-supported-types-examples",
chore: Sort workspace members
2018-07-25 23:44:14 +03:00
"examples/hello_world",
"examples/import_js",
adds julia set example (#419) * adds julia set example * fixes indentation in *.js files * fixes *.js formatting * fixes a typo in function arguments signature
2018-07-08 18:57:19 +03:00
"examples/julia_set",
chore: Sort workspace members
2018-07-25 23:44:14 +03:00
"examples/no_modules",
Add paint example
2018-09-13 02:10:23 +03:00
"examples/paint",
Add an example of the `performance` API
2018-03-21 20:21:21 +03:00
"examples/performance",
Implement support for WebAssembly threads ... and add a parallel raytracing demo! This commit adds enough support to `wasm-bindgen` to produce a workable wasm binary *today* with the experimental WebAssembly threads support implemented in Firefox Nightly. I've tried to comment what's going on in the commits and such, but at a high level the changes made here are: * A new transformation, living in a new `wasm-bindgen-threads-xform` crate, prepares a wasm module for parallel execution. This performs a number of mundane tasks which I hope to detail in a blog post later on. * The `--no-modules` output is enhanced with more support for when shared memory is enabled, allowing passing in the module/memory to initialize the wasm instance on multiple threads (sharing both module and memory). * The `wasm-bindgen` crate now offers the ability, in `--no-modules` mode, to get a handle on the `WebAssembly.Module` instance. * The example itself requires Xargo to recompile the standard library with atomics and an experimental feature enabled. Afterwards it experimentally also enables threading support in wasm-bindgen. I've also added hopefully enough CI support to compile this example in a builder so we can upload it and poke around live online. I hope to detail more about the technical details here in a blog post soon as well!
2018-10-05 06:00:23 +03:00
"examples/raytrace-parallel",
examples: Add a requestAnimationFrame loop example
2018-12-10 23:50:19 +03:00
"examples/request-animation-frame",
Adding in TODO MVC example using web-sys
2018-10-13 03:21:14 +03:00
"examples/todomvc",
Add an example of namespaced APIs By creating wasm modules from Rust!
2018-03-23 03:39:48 +03:00
"examples/wasm-in-wasm",
Reorganize and rewrite examples This commit is a large-ish scale reorganization of our examples. The main goal here is to have a dedicated section of the guide for example, and all examples will be listed there. Each example's `README` is now just boilerplate pointing at the guide along with a blurb about how to run it. Some examples like `math` and `smorgasboard` have been deleted as they didn't really serve much purpose, and others like `closures` have been rewritten with `web-sys` instead of hand-bound bindings. Overall it's hoped that this puts us in a good and consistent state for our examples, with all of them being described in the guide, excerpts are in the guide, and they're all relatively idiomatically using `web-sys`.
2018-09-21 02:20:42 +03:00
"examples/wasm2js",
Initial example of using the WebAudio APIs from web-sys Part of #443
2018-08-17 05:30:46 +03:00
"examples/webaudio",
Create basic WebGL example
2018-09-16 09:28:15 +03:00
"examples/webgl",
Migrate `#![no_std]` tests to `wasm` This required getting a little creative in a few places, but otherwise these tests shouldn't need the test builder any more.
2018-08-06 21:08:35 +03:00
"tests/no-std",
Rewrite the README using Webpack Right now Webpack probably has the most mature support for loading wasm modules, so let's show off how to do that! Additionally this commits hello world as an example to the repository.
2018-03-03 07:11:30 +03:00
]
Compile in release mode with LTO on Should help get some nice size savings!
2018-03-21 01:27:45 +03:00
Add a test harness to directly execute wasm tests (#524) * Add a test harness to directly execute wasm tests This commits adds a few new crates and infrastructure to enable comands like: cargo test --target wasm32-unknown-unknown The intention here is to make it as low-friction as possible to write wasm tests and also have them execute in a reasonable amount of time. Eventually this is also hopefully enough support to do things like headless testing! For now though this is defintely MVP status rather than fully fleshed out. There's some more information at `crates/test/README.md` about how it works and how to use it, but for now this is mainly intended to play around with locally in this repository for our own tests. * Port a numbe of `js-sys` tests to the new test framework This commit ports a number of existing tests for the `js-sys` crate over to the new test framework created in the previous commit, showing off how they can be executed as well as drastictlly simplifying the tests themselves! This is intended to be a proof of concept for now which we can refine over time. This should also show off that it's possible to incrementally move over to the new test framework.
2018-07-20 21:47:49 +03:00
[patch.crates-io]
wasm-bindgen = { path = '.' }
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 22:14:25 +03:00
wasm-bindgen-futures = { path = 'crates/futures' }
js-sys = { path = 'crates/js-sys' }
web-sys = { path = 'crates/web-sys' }
Reference in New Issue Copy Permalink