CodeVetter · Repo Unpack · Data flow
pact-foundation/pact-js
Consumer inputs become native interaction declarations rather than a JavaScript implementation of contract matching. Native mock servers or reified messages feed application callbacks, and successful orchestration writes contracts to disk. Provider verification routes native requests through JavaScript middleware, state callbacks, and message producers before returning results to the caller.
- matcherValueOrString preserves string inputs and JSON-stringifies other values; RequestBuilder translates query/header arrays into indexed native withQuery/withRequestHeader calls and serializes JSON bodies.
- Status matchers split into a concrete example passed to withStatus and status matching rules passed to withResponseMatchingRules; ordinary matcher reification recursively extracts examples.
- Explicit Rules inputs are checked for recognized parts and rule-array/path structure, then converted to part/path/matchers maps; conversion removes pact:generator:type and emits entries only for truthy rule.path.
- V4 HTTP executeTest captures callback errors, reads native mismatches and match success, and on its normal success branch writes a pact before mock-server cleanup, plugin cleanup, and parent reset.
- Asynchronous reification parses native JSON into contents.content plus metadata and base64-decodes content when the builder marked it binary; synchronous callbacks receive native request and response contents directly.
- Provider-state POST bodies become ProviderState values; setupStates selects stateHandlers[state.state], invokes setup or teardown with params, and returns callback data as JSON for native verification.
- The verification proxy parses JSON, form, and raw bodies before requestFilter; forwarding reconstructs Buffers or JSON objects into a readable body stream and uses providerBaseUrl, TLS options, and HTTPS_PROXY/HTTP_PROXY.
- /_messages dispatches by description, copies request metadata, decodes encoded synchronous content, and invokes the producer; metadata-bearing outputs become base64 JSON headers plus a content-type-aware response, while errors return HTTP 500.