FuelLabs/fuels-rs

Recent inclusion of `fuel-chain-config` prevents WASM builds

Open

Aperta il 15 dic 2022

Vedi su GitHub
 (2 commenti) (0 reazioni) (0 assegnatari)Rust (43.211 star) (1360 fork)batch import
bughelp wantedwasm

Descrizione

The recent inclusion of fuel-chain-config in fuels-types has led to an inability to build for the wasm32-unknown-unknown target for packages depending on said crate; this is due to mio being present in the dependency graph by way of fuel-core-interfaces and its dependence on tokio. More information can be found here: https://github.com/FuelLabs/fuel-indexer/issues/423. We rely on fuels-core/fuels-types pretty heavily for our indexing functionality, so any help would be appreciated.

Guida contributor

Tech stack
rustwasm
Dominio
build system
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
4
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-2 days
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
fresh
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
Rust programmingCargo dependency managementWASM cross compilation
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
35
Direzione di ricerca
Investigate the dependency chain from fuel chain config through fuel core interfaces and tokio to mio. Consider adding conditional compilation or feature flags in fuels types or fuel chain config to exclude tokio and mio when targeting wasm32 unknown unknown. Refer to issue https://github.com/FuelLabs/fuel indexer/issues/423 for prior discussion.