Support and Troubleshooting

CORS and credentials

Check the backend policy before blaming the client. Cross-site cookies require credentials: "include", SameSite=None, Secure, and compatible CORS headers.

Unresolved types

Check the npm installation, the tarball content, and the consuming project's moduleResolution mode. Types must come from the package, not from a local development path.

Inconsistent cache

Limit cache to idempotent GET calls, set stable tags, and invalidate after mutation. Persistent inconsistency often comes from a cache key that is too broad or from a tag that is never invalidated.

Custom guard blocks the request

A guard that lets the request continue must call next(ctx). A guard that replays a request must verify that the body is replayable and that the call does not loop on auth or refresh.

Notifications are too noisy

Filter with defaults.shouldNotify. Form-level 400 errors should often stay on the page, while network errors, 401 responses, and 5xx errors can be global.