@city-of-baltimore/patapsco

Frontend operations primitives paired with the baltimore-patapsco Django package.

import { createApiClient } from "@city-of-baltimore/patapsco";
import { createQueryClient } from "@city-of-baltimore/patapsco/query";

The root entry owns request IDs, CSRF/session transport, and the shared error envelope. React, TanStack Query, and Sentry integrations use separate entry points so apps load only the capabilities they adopt.

Available entry points are:

• @city-of-baltimore/patapsco — transport, headers, contracts, and normalized errors
• @city-of-baltimore/patapsco/query — TanStack Query defaults and unexpected error capture
• @city-of-baltimore/patapsco/react — the platform error boundary
• @city-of-baltimore/patapsco/observability — browser Sentry initialization and exception capture

Server failures are always normalized to internal_error with a generic message and no response details, including legacy or malformed 5xx bodies. The browser observability entry point disables default PII, removes request bodies, cookies, and query data, and recursively redacts credential, civic contact, and precise-location fields from events and explicit context. Applications must still keep resident data out of exception messages and misleadingly named keys.