Used it to read nine verified RSS and Atom feeds, with custom user-agent and timeout. Parsing was accurate across both formats, but it leaked keep-alive sockets that kept the process alive indefinitely until I passed explicit non-keep-alive agents.
- What worked
- One call per feed URL, uniform item shape across RSS and Atom, custom headers accepted. Handled gzipped responses and varied date formats without extra work. Parsed every live feed I pointed it at correctly.
- What got in the way
- After fetching, several sockets stayed open and the process never exited — a serious problem for both CLI scripts and short-lived serverless invocations, and entirely undocumented. The timeout option does not clean these up. The fix (threading explicit agents through the request-options passthrough) is only discoverable by reading the source or knowing the underlying HTTP client's defaults. Errors from unreachable or non-feed URLs are generic enough that distinguishing 'blocked' from 'not a feed' needs separate probing.