Add TypeScript definitions for package exports

[Copilot]

This PR adds TypeScript type definitions to the @exodus/replay package, providing type safety for TypeScript users.

Changes Made

Individual Type Definition Files

Created separate .d.ts files for each export module:

• fetch.d.ts: Type definitions for fetch-related exports

  • FetchRecorderOptions interface
  • Function signatures for fetchRecorder, fetchReplayer, fetchApi

• websocket.d.ts: Type definitions for WebSocket-related exports

  • WebSocketRecorderOptions and WebSocketReplayerOptions interfaces
  • Function signatures for WebSocketRecorder, WebSocketReplayer

• util.d.ts: Type definitions for utility exports

  • PrettyJSONOptions interface
  • Function signature for prettyJSON

• index.d.ts: Main entry point that re-exports types and functions from individual modules

Package Configuration

• package.json: Updated exports with types field for each submodule, enabling proper TypeScript resolution for both main and submodule imports
• .eslintignore: Added *.d.ts to skip linting TypeScript definition files

Design Decisions

The type definitions only export package-specific interfaces and function signatures. Standard DOM/Web API types (like Response, Request, Headers, WebSocket, MessageEvent, etc.) are not re-exported because:

• They are already available to TypeScript users through the standard lib definitions
• They are not exported by the JavaScript modules
• Re-exporting them would be redundant and misleading

Usage

TypeScript users now get full type safety for both main and submodule imports:

// Import from main module
import { fetchRecorder, type FetchRecorderOptions } from '@exodus/replay'

// Or import directly from submodules
import { fetchRecorder } from '@exodus/replay/fetch'
import { WebSocketReplayer } from '@exodus/replay/websocket'

Testing

• ✅ All TypeScript definitions validated with tsc
• ✅ All existing tests pass (60/60 replay tests)
• ✅ Linter passes with no errors
• ✅ Security scan (CodeQL) found 0 vulnerabilities

The changes are purely additive type definitions with no runtime impact.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Types</issue_title>
<issue_description>Re-export existing DOM / Node.js types where possible</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Types #4

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[ChALkeR]

@copilot add types to each export individually

[Copilot]

@copilot add types to each export individually

Done. Added individual type definition files for each export:

• fetch.d.ts - Types for fetch API exports
• websocket.d.ts - Types for WebSocket exports
• util.d.ts - Types for utility exports
• index.d.ts - Re-exports all types from individual modules

Updated package.json exports to specify types for each submodule. Commit: 4c3b069

[ChALkeR]

@copilot These are not needed, don't do useless things

[Copilot]

Removed. util.js only exports prettyJSON, so the binary data type re-exports were unnecessary. Commit: 9dcd9c8

[ChALkeR]

@copilot don't export other useless things too

[Copilot]

Removed. Standard DOM/Web API types (Response, Request, Headers, WebSocket, MessageEvent, etc.) are already available through TypeScript's lib definitions and don't need to be re-exported. Only package-specific interfaces and function signatures remain. Commit: 944d66f