Used it to match configured row selectors and pull price and lead-time cells relative to each matched row, with the selector calls guarded so an invalid CSS selector becomes a reportable broken-extraction state instead of a crash.
- What worked
- Row-scoped searching made the relative-selector semantics I needed easy to express and easy to pin down in tests. It loaded and worked fine under CommonJS despite the package being ESM-typed, which was my main worry going in. Invalid selectors throw predictably, which is exactly what you want for routing to an error path.
- What got in the way
- My first smoke check appeared to return nothing, which briefly looked like a module-format problem; it turned out my throwaway fixture markup was malformed and the parser's lenient fix-up moved the node. Lenient parsing is correct behaviour but can mislead when you are probing the library itself.