serde 1.0.221 introduced serde_core into the build graph, which should render explicitly depending on serde_derive for faster build times an obsolote method. Besides, I'm not even sure if that worked for us. My hunch is that at least one of our deps would have `serde` with derive feature enabled.. and then, most of the crates using `serde_derive` explicitly were also depending on gpui, which depended on `serde`.. thus, we wouldn't have gained anything from explicit dep on `serde_derive` Release Notes: - N/A
51 lines
1.0 KiB
TOML
51 lines
1.0 KiB
TOML
[package]
|
|
name = "terminal"
|
|
version = "0.1.0"
|
|
edition.workspace = true
|
|
publish.workspace = true
|
|
license = "GPL-3.0-or-later"
|
|
|
|
[features]
|
|
test-support = [
|
|
"collections/test-support",
|
|
"gpui/test-support",
|
|
"settings/test-support",
|
|
]
|
|
|
|
[lints]
|
|
workspace = true
|
|
|
|
[lib]
|
|
path = "src/terminal.rs"
|
|
doctest = false
|
|
|
|
[dependencies]
|
|
alacritty_terminal.workspace = true
|
|
anyhow.workspace = true
|
|
collections.workspace = true
|
|
futures.workspace = true
|
|
gpui.workspace = true
|
|
libc.workspace = true
|
|
release_channel.workspace = true
|
|
schemars.workspace = true
|
|
serde.workspace = true
|
|
settings.workspace = true
|
|
sysinfo.workspace = true
|
|
smol.workspace = true
|
|
task.workspace = true
|
|
theme.workspace = true
|
|
thiserror.workspace = true
|
|
util.workspace = true
|
|
regex.workspace = true
|
|
urlencoding.workspace = true
|
|
workspace-hack.workspace = true
|
|
itertools.workspace = true
|
|
|
|
[target.'cfg(windows)'.dependencies]
|
|
windows.workspace = true
|
|
|
|
[dev-dependencies]
|
|
gpui = { workspace = true, features = ["test-support"] }
|
|
rand.workspace = true
|
|
url.workspace = true
|