sandbox-fetch-docs

Verify a library's API against official documentation by comparing function signatures, types, and behavior between the published docs and the local code implementation to identify discrepancies. This process catches contract drift and bugs caused by misleading documentation.

API contract verification is the process of validating that a library's actual implementation matches its documented public API. You need it to catch contract drift, validate dependencies before upgrading, and ensure version compatibility across releases.

Yes, you can check version compatibility for node_modules by comparing local package sources against public repository docs to ensure changes across releases maintain expected interfaces and validate behavior after updates.

Validate new dependencies in large projects by aligning the local API surface of a package with its published documentation to quickly report any mismatches before integrating the upgrade.

Yes, you need local node_modules and package sources to verify API discrepancies, as the process requires comparing local implementation code against public repository documentation to detect mismatches in signatures and usage examples.

Code breaks after a dependency update when the actual implementation diverges from the official documentation. Comparing local package sources against published docs reveals these API contract discrepancies and misleading documentation.