rustwasm/wasm-bindgen
1
0
Fork 0
mirror of https://github.com/rustwasm/wasm-bindgen.git synced 2025-01-08 14:13:51 +03:00
Code Issues Actions Packages Projects Releases Wiki Activity
8e992dc906
wasm-bindgen/Cargo.toml

111 lines
3.1 KiB
TOML
Raw Normal View History

Initial commit
2017-12-15 06:31:01 +03:00
[package]
name = "wasm-bindgen"
Prepare v0.2.91 release (#3829)
2024-02-06 14:37:22 +03:00
version = "0.2.91"
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"]
Update license field following SPDX 2.1 license expression standard (#3529)
2023-07-19 11:57:34 +03:00
license = "MIT OR Apache-2.0"
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"
Add a "nightly only" warning to documentation Official documentation is now available at https://rustwasm.github.io/docs/wasm-bindgen/, so let's leave this git repository's documentation purely for our own previewing purposes.
2019-03-07 18:42:47 +03:00
homepage = "https://rustwasm.github.io/"
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.
"""
Migrate all crates to the 2018 edition Most of the CLI crates were already in the 2018 edition, and it turns out that one of the macro crates was already in the 2018 edition so we may as well move everything to the 2018 edition! Always nice to remove those `extern crate` statements nowadays! This commit also does a `cargo fmt --all` to make sure we're conforming with style again.
2019-03-26 18:00:16 +03:00
edition = "2018"
use Vec's try_reserve_exact method (#3656)
2023-10-14 00:59:22 +03:00
rust-version = "1.57"
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]
[WIP] Add support for unstable WebIDL (#1997) * Re-enable WebGPU WebIDL as experimental * Add `web_sys_unstable_apis` attribute * Add test for unstable WebIDL * Include unstable WebIDL in docs.rs builds * Add docs and doc comment for unstable APIs * Add unstable API checks to CI
2020-02-27 01:30:11 +03:00
features = ["serde-serialize"]
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
Disable test for lib/doctest, there are none!
2018-02-02 19:10:48 +03:00
[lib]
test = 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"]
Changing from uluru to HashMap
2019-07-18 22:50:31 +03:00
enable-interning = ["std"]
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"]
Fix large pointers from WASM (#3310) Pointers being passed from WASM to JS are interpreted as signed, so large pointers ended up negative. This prevented WASM programs from allocating more than 2GB. To fix it we make all pointers unsigned (via >>> 0) for all malloc/realloc calls and inside shim functions. Ideally we would have an abstraction that guarantees we catch all cases, but that would require a major refactor. To test it we add gg-alloc as an optional system allocator for wasm-bindgen-test. It only allocates in the upper 2GB range and was made to test this exact issue but was never upstreamed. Fixes #2388 Fixes #2957
2023-02-17 18:10:06 +03:00
# Enables gg-alloc as system allocator when using wasm-bindgen-test to check that large pointers
# are handled correctly
gg-alloc = ["wasm-bindgen-test/gg-alloc"]
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!
Fix large pointers from WASM (#3310) Pointers being passed from WASM to JS are interpreted as signed, so large pointers ended up negative. This prevented WASM programs from allocating more than 2GB. To fix it we make all pointers unsigned (via >>> 0) for all malloc/realloc calls and inside shim functions. Ideally we would have an abstraction that guarantees we catch all cases, but that would require a major refactor. To test it we add gg-alloc as an optional system allocator for wasm-bindgen-test. It only allocates in the upper 2GB range and was made to test this exact issue but was never upstreamed. Fixes #2388 Fixes #2957
2023-02-17 18:10:06 +03:00
xxx_debug_only_print_generated_code = [
"wasm-bindgen-macro/xxx_debug_only_print_generated_code",
]
Add a feature for printing the macro's generated code (#212)
2018-05-26 02:17:54 +03:00
Initial commit
2017-12-15 06:31:01 +03:00
[dependencies]
Prepare v0.2.91 release (#3829)
2024-02-06 14:37:22 +03:00
wasm-bindgen-macro = { path = "crates/macro", version = "=0.2.91" }
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 }
Update cfg-if requirement from 0.1.9 to 1.0.0 (#2326) Updates the requirements on [cfg-if](https://github.com/alexcrichton/cfg-if) to permit the latest version. - [Release notes](https://github.com/alexcrichton/cfg-if/releases) - [Commits](https://github.com/alexcrichton/cfg-if/compare/0.1.9...1.0.0) Signed-off-by: dependabot-preview[bot] <support@dependabot.com> Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
2020-10-07 13:43:16 +03:00
cfg-if = "1.0.0"
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]
Prepare v0.2.91 release (#3829)
2024-02-06 14:37:22 +03:00
js-sys = { path = 'crates/js-sys', version = '0.3.68' }
wasm-bindgen-test = { path = 'crates/test', version = '=0.3.41' }
wasm-bindgen-futures = { path = 'crates/futures', version = '=0.4.41' }
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 = [
Add a page of microbenchmarks for wasm-bindgen This commit starts to add a page of microbenchmarks for wasm-bindgen which we can hopefully track and compare over time. Right now it's primarily focused on data collection, making it easy to collect data across a number of benchmarks for comparison. It doesn't currently do much in the way of actually comparing the results for you (aka drawing pretty graphs), so let's left for a future step. It's hoped though that we can use this to track performance improvements as well as ensuring that they work over time!
2019-04-29 23:32:01 +03:00
"benchmarks",
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",
Test examples in CI (#3015) * Add a test that examples don't throw any errors TODO: - run all the tests, not just the ones which use webpack (also an issue with CI) - fix webxr test - run in CI - share WebDriver instance between tests - maybe ditch async, since we don't really need it here and it adds a bunch of dependencies and build time. * Disable testing WebXR example It isn't supported in Firefox yet, which is where we're running our tests. * Test examples that aren't built with webpack * Remove `WEBDRIVER` environment variable It wouldn't have worked anyway because at least for the moment, I'm using one WebDriver session per test, and Firefox at least only allows one session to be connected. I would like to make them share a session, in which case I could add this back, but I can't right now because Firefox hasn't implemented `LogEntry.source` yet, which is needed to figure out which log entries should fail which tests. * Run in CI * Use `Once` instead of `Mutex` * Build `webxr` and `synchronous-instantiation` in CI Although we can't test them, we can still build them. * Add missing '`' * Fix running of tests * Only include dev deps when not compiling for wasm * oops, those are the native tests * Create build dirs before copying to them * Install binaryen * decompress * Follow redirects * Set `PATH` properly * Use an absolute path * Don't symlink `node_modules` and fix artifact download * Enable `web_sys_unstable_apis` This is needed for the `webxr` example. * Increase timeout to 10s * Increase timeout to 20s This seems excessive but 10s is still sometimes failing. * Disable testing the webgl example * Add binaryen to PATH directly after installing * Properly download the raytrace example artifacts * Disable example tests instead of enabling everything else * Move to a separate `example-tests` crate
2022-08-05 18:51:41 +03:00
"crates/example-tests",
Start testing TypeScript output on CI This commit starts to add some simple tests for our TypeScript output of the wasm-bindgen CLI, currently just running `tsc` to make sure syntax looks good and types are emitted as expected. This'll hopefully be able to get expanded over time with bug reports as they come in as well as ensure that we don't regress anything in egregious manners! Closes #922
2019-03-05 19:33:27 +03:00
"crates/typescript-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",
address pr comments
2020-06-02 11:53:21 +03:00
"examples/deno",
Add an example of DOM access
2018-03-21 18:26:00 +03:00
"examples/dom",
Start testing TypeScript output on CI This commit starts to add some simple tests for our TypeScript output of the wasm-bindgen CLI, currently just running `tsc` to make sure syntax looks good and types are emitted as expected. This'll hopefully be able to get expanded over time with bug reports as they come in as well as ensure that we don't regress anything in egregious manners! Closes #922
2019-03-05 19:33:27 +03:00
"examples/duck-typed-interfaces",
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",
Reorganize the import_js example
2019-03-25 23:49:05 +03:00
"examples/import_js/crate",
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",
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 example with WASM audio worklet (#3017)
2022-08-13 13:12:17 +03:00
"examples/wasm-audio-worklet",
Add an example of namespaced APIs By creating wasm modules from Rust!
2018-03-23 03:39:48 +03:00
"examples/wasm-in-wasm",
Create wasm-in-wasm-imports example (#2229)
2020-07-08 17:17:20 +03:00
"examples/wasm-in-wasm-imports",
Add wasm in web worker example (#2556) This commit adds a parallel execution example in which we spawn a web worker with `web_sys`, run WASM code in the web worker and interact between the main thread and the web worker. It is intended to add an easy starting point for parallel execution with WASM, complementing the more involved parallel raytrace example. Related to GitHub issue #2549 Co-authored-by: Simon Gasse <sgasse@users.noreply.github.com>
2021-05-18 17:46:30 +03:00
"examples/wasm-in-web-worker",
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",
Upgrade the webpack-based examples' npm dependencies (move to webpack 5) (#2651) * Upgraded the webpack examples' npm dependencies which (among other things) upgrades them to webpack 5 For the weather_report, had to choose the syncWebAssembly experiment, whereas the rest works fine with asyncWebAssembly * Fix the weather report example compilation by adding it to the main workspace. This currently fails with: error: current package believes it's in a workspace when it's not: current: <project-root>/examples/weather_report/Cargo.toml workspace: <project-root>/Cargo.toml * Fix the build of the webxr example with webpack 5 * run cargo fmt
2021-08-10 17:43:42 +03:00
"examples/weather_report",
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",
[Examples] Add WebRTC DataChannel example (#2131) * Add WebRTC DataChannel example * Add guide * Fix format * Use webpack to build example
2020-05-12 22:00:33 +03:00
"examples/webrtc_datachannel",
added websockets example
2019-05-20 02:01:25 +03:00
"examples/websockets",
Webxrdevice (#2000) * crates/web-sys/webidls/enabled/WebXRDevice.webidl * Add WebXR Web IDL. * Add WebXr example. * Workaround in WebXR for FrozenArray and XRWebGLLayer constructor. * Remove commented code. * Attempt to improve WebXr example. * Add WebXr as unstable WebIDL. * Fixes for XRWebGLLayer. * Tidy up WebXR example code. * Update WebXr example docs. Co-authored-by: Kev Kirkland <kev.kirkland@elucidata.co.uk>
2020-03-17 17:14:05 +03:00
"examples/webxr",
Tweak introductory and deployment documentation. This commit rejiggers some documentation of `wasm-bindgen` in a few significant ways: * The main landing page now has text and links to the Game of Life tutorial and `wasm-pack`. * The "whirlwind tour" was deleted as it wasn't really serving any purpose that the Game of Life plus the later references weren't already serving. * The "no modules" example was renamed to "without a bundler" * A dedicated section on "Deployment" was added which replaces the previous "No ES Modules" page. This is hopefully more descriptive and also prominently mentions the various options for deployment.
2019-02-21 22:49:08 +03:00
"examples/without-a-bundler",
Implement the local JS snippets RFC This commit is an implementation of [RFC 6] which enables crates to inline local JS snippets into the final output artifact of `wasm-bindgen`. This is accompanied with a few minor breaking changes which are intended to be relatively minor in practice: * The `module` attribute disallows paths starting with `./` and `../`. It requires paths starting with `/` to actually exist on the filesystem. * The `--browser` flag no longer emits bundler-compatible code, but rather emits an ES module that can be natively loaded into a browser. Otherwise be sure to check out [the RFC][RFC 6] for more details, and otherwise this should implement at least the MVP version of the RFC! Notably at this time JS snippets with `--nodejs` or `--no-modules` are not supported and will unconditionally generate an error. [RFC 6]: https://github.com/rustwasm/rfcs/pull/6 Closes #1311
2019-02-25 22:11:30 +03:00
"examples/without-a-bundler-no-modules",
Expose helpers to allow synchronous initialization (#2924) * Expose helpers to allow synchronous initialization * fixup: fix tests
2022-06-08 22:18:05 +03:00
"examples/synchronous-instantiation",
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
]
Update cargo dependency resolver to v2 (#3358)
2023-05-08 18:19:24 +03:00
resolver = "2"
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