web.rs
rust-wasm-on-lambda-edge
web.rs | rust-wasm-on-lambda-edge | |
---|---|---|
3 | 2 | |
169 | 24 | |
- | - | |
0.0 | 9.2 | |
10 months ago | 9 days ago | |
Rust | Rust | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
web.rs
- JavaScript-WebAssembly interop library for C, Rust, Assemblyscript
-
WASM/JS- which toolchain/libraries to use?
You should also take a look at https://wasm.js.org/ : an interesting, lightweight approach. Compared to wasm-bindgen, it feels more like a library while wasm-bindgen feels more like a framework.
- class_names - porting a ridiculously popular library from JavaScript into Rust for expressing list of CSS class names
rust-wasm-on-lambda-edge
-
WASM/JS- which toolchain/libraries to use?
AWS Lambda@Edge is much, much more convoluted because IIRC you can only run node and python there. In other words, you have to use some glue to make it work.
-
Rust/Wasm on AWS Lambda@Edge
I adopted a rollup based approach, since it's quite easy to get configured and also something we use at work. I always found webpack a little bit too cumbersome, and parcel is just yet another new kid on the block. I'm pretty sure you can adjust the project to your needs. All we need here is: compile TS to JS and bundle up everything into a single JS file. In the past I found the WebAssembly dependency management very tricky, in the end I used a plain "move the .wasm file into the final bundle" approach, which just works fine, because I did not want to inline the WebAssembly code (as most plugins try). Maybe you have a smarter solution for that, please open a pull-request in the repo. Just keep in mind: wasm-bindgen creates already a pretty decent module loader, so there is no need to work around that, but I fail to get any of these bundlers to move the wasm files along with it into the bundle output directory.
What are some alternatives?
webpack - A bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
serde-wasm-bindgen - Native integration of Serde with wasm-bindgen
coldsnap - A command line interface for Amazon EBS snapshots
aws-lambda-events - Rust event types for AWS Lambda
resvg-js - A high-performance SVG renderer and toolkit, powered by Rust based resvg and napi-rs.
wasm-bindgen - Facilitating high-level interactions between Wasm modules and JavaScript
rs2ts - Rust structs and enums to TypeScript interfaces and enums
wasm-pack - 📦✨ your favorite rust -> wasm workflow tool!
bitque - A simplified Jira clone built with seed.rs and actix
wrangler-legacy - 🤠 Home to Wrangler v1 (deprecated)
rust-typescript-template - 📝 A template for creating WASM + Typescript + Rust workflow libraries.