mirror of
https://github.com/matrix-org/matrix-rust-sdk.git
synced 2026-05-25 01:02:20 -04:00
ee648144a2
Why? Because `napi` and `wasm-bindgen` are too different. At this step, the most notable bugs are the way `napi` is handling its proc macros. There is too much conflicts when used with `#[cfg_attr]`. It makes the code repetitive and harder to read and to understand (and also to compile, we must be very careful). But on the short-term, quickly, we will see more notable differences between `wasm-bindgen` and `napi`, e.g. with array (in `wasm-bindgen`, we can downcast array items into particular types, with `napi` it's going to be a very different code). Instead of fighting the proc macros bugs now, and having to split the code later inside the same crate, we believe it's a good idea to split the code now into 2 crates. At first we will see obvious code duplications, but on the short-term, the code is likely to be more and more different.
28 lines
496 B
JSON
28 lines
496 B
JSON
{
|
|
"name": "matrix-sdk-crypto",
|
|
"version": "0.5.0",
|
|
"main": "index.js",
|
|
"types": "index.d.ts",
|
|
"napi": {
|
|
"name": "matrix-sdk-crypto",
|
|
"triples": {
|
|
"additional": [
|
|
"aarch64-apple-darwin"
|
|
]
|
|
}
|
|
},
|
|
"license": "MIT",
|
|
"devDependencies": {
|
|
"@napi-rs/cli": "^2.9.0",
|
|
"ava": "^4.2.0"
|
|
},
|
|
"engines": {
|
|
"node": ">= 10"
|
|
},
|
|
"scripts": {
|
|
"artifacts": "napi artifacts",
|
|
"build": "napi build --platform --release",
|
|
"test": "ava"
|
|
}
|
|
}
|