You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi!
Cargo is notorious for not pruning the dependencies for target_family.
That currently means that a user of simd-json that will never compiler for wasm will still have js_sys in its lockfile because of:
[target.'cfg(target_family="wasm")'.dependencies]
getrandom = { version = "0.2", features = ["js"] }
A common way to get around that is to create a feature wasm and put the getrandom as optional.
This is really a cargo problem, but until they fix it that is what is usually recommended.
The text was updated successfully, but these errors were encountered:
Hi!
Cargo is notorious for not pruning the dependencies for
target_family
.That currently means that a user of
simd-json
that will never compiler for wasm will still havejs_sys
in its lockfile because of:A common way to get around that is to create a feature
wasm
and put thegetrandom
as optional.This is really a cargo problem, but until they fix it that is what is usually recommended.
The text was updated successfully, but these errors were encountered: