mirror of
https://github.com/lightningdevkit/rust-lightning.git
synced 2025-03-10 05:33:40 +01:00
1a18b881bb
We have some downstream folks who are using LDK in wasm compiled via the normal rust wasm path. To ensure nothing breaks they want to use `no-std` on the lightning crate, disabling time calls as those panic. However, the HTTP logic in `lightning-transaction-sync` gets automatically stubbed out by the HTTP client crates when targeting wasm via `wasm_bindgen`, so it works fine despite the std restrictions. In order to make both work, `lightning-transaction-sync` can remain `std`, but needs to not automatically enable the `std` flag on the `lightning` crate, ie by setting `default-features = false`. We do so here.
34 lines
1.1 KiB
TOML
34 lines
1.1 KiB
TOML
[package]
|
|
name = "lightning-transaction-sync"
|
|
version = "0.0.113"
|
|
authors = ["Elias Rohrer"]
|
|
license = "MIT OR Apache-2.0"
|
|
repository = "http://github.com/lightningdevkit/rust-lightning"
|
|
description = """
|
|
Utilities for syncing LDK via the transaction-based `Confirm` interface.
|
|
"""
|
|
edition = "2018"
|
|
|
|
[package.metadata.docs.rs]
|
|
all-features = true
|
|
rustdoc-args = ["--cfg", "docsrs"]
|
|
|
|
[features]
|
|
default = []
|
|
esplora-async = ["async-interface", "esplora-client/async", "futures"]
|
|
esplora-blocking = ["esplora-client/blocking"]
|
|
async-interface = []
|
|
|
|
[dependencies]
|
|
lightning = { version = "0.0.113", path = "../lightning", default-features = false }
|
|
bitcoin = { version = "0.29.0", default-features = false }
|
|
bdk-macros = "0.6"
|
|
futures = { version = "0.3", optional = true }
|
|
esplora-client = { version = "0.3.0", default-features = false, optional = true }
|
|
|
|
[dev-dependencies]
|
|
lightning = { version = "0.0.113", path = "../lightning", features = ["std"] }
|
|
electrsd = { version = "0.22.0", features = ["legacy", "esplora_a33e97e1", "bitcoind_23_0"] }
|
|
electrum-client = "0.12.0"
|
|
once_cell = "1.16.0"
|
|
tokio = { version = "1.14.0", features = ["full"] }
|