[package]
name = "custom-pages-fuzz"
version = "0.0.0"
publish = false
edition = "2024"

[package.metadata]
cargo-fuzz = true

[dependencies]
# `arbitrary` with `derive` is what lets a target take `&str` instead of
# `&[u8]`. Both inputs here are text grammars -- HTML and CSS -- and byte input
# would spend most of the fuzzer's budget rediscovering UTF-8 before it reached
# an angle bracket or a brace.
libfuzzer-sys = { version = "0.4", features = ["arbitrary-derive"] }

[dependencies.custom-pages]
path = ".."

# `fuzz/Cargo.lock` IS COMMITTED, and it is load-bearing rather than incidental.
# A fresh resolve of this crate picks `parcel_selectors` 0.28.3, whose patch bump
# moved it to `cssparser` 0.37 while the exactly-pinned `lightningcss`
# alpha.71 is still on 0.33. The two then meet in one graph and the build fails
# with 61 type errors inside lightningcss, none of them about anything in this
# tree. That is the same pre-1.0 hazard the parent manifest documents on its
# lightningcss pin, arriving one level down where the exact pin cannot reach it,
# so the lock is what holds `parcel_selectors` at 0.28.2. Do not `cargo update`
# this directory without building afterwards.

[[bin]]
name = "html"
path = "fuzz_targets/html.rs"
test = false
doc = false
bench = false

[[bin]]
name = "css"
path = "fuzz_targets/css.rs"
test = false
doc = false
bench = false