fix: resolve wasm-bindgen version conflicts and fiber API compatibility issues #79
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem Description
Fixed wasm-bindgen version conflicts and fiber API compatibility issues that were causing compilation errors.
Changes Made
Update workspace config with resolver = "2" and wasm-bindgen version constraints
Fix chainbound fiber client to adapt to new fiber API
subscribe_new_txs→subscribe_new_transactionsExecutionHeadersstream typeUpdate fiber dependency from 0.3.3 to 0.8.1
Fix alloy type import paths to resolve compilation errors
alloy::consensus::transaction::RecoveredpathAdd required ethereum-consensus dependency
Technical Details
Main Issues Fixed:
Files Modified:
Cargo.toml: Added workspace resolver and wasm-bindgen version constraintscrates/clients/chainbound/Cargo.toml: Updated dependency versionscrates/clients/chainbound/src/fiber.rs: Fixed API calls and type importsTesting
Impact
Related Issues
Closes #[add issue number if applicable]
Note: This PR resolves compilation issues and updates dependencies to their latest compatible versions while maintaining functionality.