| 1 |
[package] |
| 2 |
name = "custom-pages-fuzz" |
| 3 |
version = "0.0.0" |
| 4 |
publish = false |
| 5 |
edition = "2024" |
| 6 |
|
| 7 |
[package.metadata] |
| 8 |
cargo-fuzz = true |
| 9 |
|
| 10 |
[dependencies] |
| 11 |
# `arbitrary` with `derive` is what lets a target take `&str` instead of |
| 12 |
# `&[u8]`. Both inputs here are text grammars -- HTML and CSS -- and byte input |
| 13 |
# would spend most of the fuzzer's budget rediscovering UTF-8 before it reached |
| 14 |
# an angle bracket or a brace. |
| 15 |
libfuzzer-sys = { version = "0.4", features = ["arbitrary-derive"] } |
| 16 |
|
| 17 |
[dependencies.custom-pages] |
| 18 |
path = ".." |
| 19 |
|
| 20 |
# `fuzz/Cargo.lock` IS COMMITTED, and it is load-bearing rather than incidental. |
| 21 |
# A fresh resolve of this crate picks `parcel_selectors` 0.28.3, whose patch bump |
| 22 |
# moved it to `cssparser` 0.37 while the exactly-pinned `lightningcss` |
| 23 |
# alpha.71 is still on 0.33. The two then meet in one graph and the build fails |
| 24 |
# with 61 type errors inside lightningcss, none of them about anything in this |
| 25 |
# tree. That is the same pre-1.0 hazard the parent manifest documents on its |
| 26 |
# lightningcss pin, arriving one level down where the exact pin cannot reach it, |
| 27 |
# so the lock is what holds `parcel_selectors` at 0.28.2. Do not `cargo update` |
| 28 |
# this directory without building afterwards. |
| 29 |
|
| 30 |
[[bin]] |
| 31 |
name = "html" |
| 32 |
path = "fuzz_targets/html.rs" |
| 33 |
test = false |
| 34 |
doc = false |
| 35 |
bench = false |
| 36 |
|
| 37 |
[[bin]] |
| 38 |
name = "css" |
| 39 |
path = "fuzz_targets/css.rs" |
| 40 |
test = false |
| 41 |
doc = false |
| 42 |
bench = false |
| 43 |
|