Files
Benjamin WoodruffandGitHub a05f664bb4 Turbopack: chore: Remove re-exports from turbopack crate (#85791)
I don't think these specific re-exports are too problematic, but we've moved away from the pattern of a few top-level crates re-exporting all of the rest of turbopack because in some cases it can make compilation performance much worse in the way that it structures the crate dependency graph.

Re-exports of "internal" crates can be useful in controlling what parts of the API is and isn't "public", but these re-exports aren't really doing that.
2025-12-02 14:33:26 -08:00

45 lines
1.2 KiB
TOML

[package]
name = "turbopack-nft"
version = "0.1.0"
description = "TBD"
license = "MIT"
edition = "2024"
autobenches = false
[[bin]]
name = "turbopack-nft"
path = "src/main.rs"
bench = false
[lib]
bench = false
[lints]
workspace = true
[dependencies]
anyhow = { workspace = true }
clap = { workspace = true, features = ["derive", "env"] }
console-subscriber = { workspace = true, optional = true }
rustc-hash = { workspace = true }
serde = { workspace = true }
swc_core = { workspace = true }
tokio = { workspace = true, features = ["full"] }
tracing = { workspace = true }
tracing-subscriber = { workspace = true, features = ["json"] }
turbo-rcstr = { workspace = true }
turbo-tasks = { workspace = true }
turbo-tasks-backend = { workspace = true }
turbo-tasks-env = { workspace = true }
turbo-tasks-fs = { workspace = true }
turbo-tasks-malloc = { workspace = true, default-features = false, features = [
"custom_allocator"
] }
turbopack = { workspace = true }
turbopack-ecmascript = { workspace = true }
turbopack-cli-utils = { workspace = true }
turbopack-core = { workspace = true }
turbopack-resolve = { workspace = true }
turbopack-trace-utils = { workspace = true }