FuelLabs/fuels-rs

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

Open

#745 opened on Dec 15, 2022

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (43,211 stars) (1,360 forks)batch import
bughelp wantedwasm

Description

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.

Contributor guide

Tech stack
rustwasm
Domain
build system
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust programmingCargo dependency managementWASM cross compilation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
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.