Our great sponsors
-
You can do it - that's actually exactly what my project is doing. I have a single repository with a Rust project, that builds the .wasm file (+ .d.ts + .js) using wasm-pack, and a Node.js project, that uses this .wasm file. There's no problem in packing that and exposing as a npm package. See parcel-bundler/lightningcss for a full blown example (it's not using wasm-pack but builds the Rust project directly).
-
You can! In https://github.com/clbarnes/nblast-rs/tree/smat , I have a cargo workspace with a rust library, then a dependent maturin project depending on that library with pyo3 bindings and some pythonic sugar around it, and a dependent rust/wasm library which takes those flattened arrays. As a proof of concept, I put the nice js interface straight into the example app, but I'd prefer to ship it as part of the library.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
Related posts
- LightningCSS Benchmark
- Help with "returns a value referencing data owned by the current function"
- An fast CSS parser, transformer, bundler, and minifier written in Rust
- Parcel-Css - A CSS parser, transformer, and minifier written in Rust.
- ParcelCSS – A CSS parser, transformer, and minifier written in Rust