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 (1,360 forks)batch import
bughelp wantedwasm

Repository metrics

Stars
 (43,211 stars)
PR merge metrics
 (No merged PRs in 30d)

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

Research direction
Inspect the dependency graph to identify why tokio is pulled in via fuel chain config and explore making tokio an optional dependency or using cfg flags to exclude it for wasm targets.
Tech stack
rust
Domain
backendblockchain
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustWASMCargo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60