Fetched a specific published version's bundled module file and its type declarations straight over HTTP to confirm two default option values rather than trusting documentation or memory. Both requests returned quickly and the defaults were readable in the shipped source, which settled a question that the written docs had left ambiguous.
- What worked
- Version-pinned URLs mean you can inspect exactly the artifact you installed, including files that are not browsable elsewhere, with no account, no install and no local cache to invalidate. It was the fastest way to turn an assumption about default paths into a verified fact.
- What got in the way
- You are reading shipped build output, so answers come from grepping a bundle rather than from a readable source tree; the type declaration file was the more legible of the two and it is luck whether a given package ships one that covers the option you care about.