We'll need two FFI layers for buttplug-rs-ffi in JS:
WASM, which is already handled via wasm-bindgen and our bindings in this repo
Neon, which we'll use for native bindings to node
For the past 3 years, we've distributed both the node module and webpack'd web module in the "buttplug" package on npm. This is now more complicated, since the WASM library will be all of Buttplug + web components (WebBluetooth, Browser websockets, etc), and the node will be neon bindings. So we need to decide whether we're shipping everything in the same package (if that's even possible?), or splitting to buttplug-web and buttplug-node and deprecating our main package.
We'll need two FFI layers for buttplug-rs-ffi in JS:
For the past 3 years, we've distributed both the node module and webpack'd web module in the "buttplug" package on npm. This is now more complicated, since the WASM library will be all of Buttplug + web components (WebBluetooth, Browser websockets, etc), and the node will be neon bindings. So we need to decide whether we're shipping everything in the same package (if that's even possible?), or splitting to buttplug-web and buttplug-node and deprecating our main package.