Fix linting / build issues

Author: ejsmith

.github/workflows/ci.yml

@@ -59,7 +59,7 @@ jobs:
 
       - name: Tests
         run: |
-          deno test --allow-net --coverage=cov/
+          deno test --allow-net --coverage=cov/ src/tests
           deno coverage cov/
 
       - name: Publish Release Package

deno.json

@@ -4,6 +4,7 @@
     "./mocks": "./src/mocks/mod.ts"
   },
   "name": "@foundatiofx/fetchclient",
+  "license": "MIT",
   "tasks": {
     "build": "deno run -A scripts/build.ts",
     "check": "deno check scripts/*.ts *.ts src/*.ts src/mocks/*.ts",
@@ -17,5 +18,20 @@
     "@std/path": "jsr:@std/path@^1.1.4",
     "zod": "npm:zod@^4.3.6"
   },
-  "exclude": ["npm", "docs"]
+  "exclude": ["docs/.vitepress", "docs/package-lock.json", "npm"],
+  "publish": {
+    "exclude": [
+      ".claude",
+      ".github",
+      ".vscode",
+      "AGENTS.md",
+      "deno.lock",
+      "docs",
+      "npm",
+      "nul",
+      "samples",
+      "scripts",
+      "src/tests"
+    ]
+  }
 }

docs/guide/caching.md

@@ -1,6 +1,7 @@
 # Caching
 
-FetchClient provides built-in response caching with TTL (time-to-live), cache tags for grouped invalidation, and programmatic cache control.
+FetchClient provides built-in response caching with TTL (time-to-live), cache
+tags for grouped invalidation, and programmatic cache control.
 
 ## Basic Caching
 
@@ -33,7 +34,8 @@ const cached = await client.getJSON<Todo>(
 
 ## Cache Keys
 
-Cache keys are arrays that get joined with colons. This makes it easy to organize and invalidate related entries:
+Cache keys are arrays that get joined with colons. This makes it easy to
+organize and invalidate related entries:
 
 ```ts
 // These cache keys become:
@@ -85,7 +87,8 @@ client.cache.clear();
 
 ## Cache Tagging
 
-Tags let you group unrelated cache entries and invalidate them together. This is useful when data relationships span different cache keys.
+Tags let you group unrelated cache entries and invalidate them together. This is
+useful when data relationships span different cache keys.
 
 ### Adding Tags
 
@@ -135,7 +138,8 @@ const entryTags = client.cache.getEntryTags(["posts", "1"]);
 ## Cache Behavior
 
 - **Automatic cleanup**: Expired entries are removed automatically when accessed
-- **Tag cleanup**: Tags are automatically cleaned up when their entries expire or are deleted
+- **Tag cleanup**: Tags are automatically cleaned up when their entries expire
+  or are deleted
 - **Memory-based**: Cache is stored in memory and clears on page refresh
 - **Per-provider**: Each `FetchClientProvider` has its own cache instance
 

docs/guide/circuit-breaker.md

@@ -1,16 +1,20 @@
 # Circuit Breaker
 
-The circuit breaker pattern prevents cascading failures when an API goes down. Instead of repeatedly hitting a failing service, the circuit breaker "opens" and immediately rejects requests, giving the service time to recover.
+The circuit breaker pattern prevents cascading failures when an API goes down.
+Instead of repeatedly hitting a failing service, the circuit breaker "opens" and
+immediately rejects requests, giving the service time to recover.
 
 ## Why Use a Circuit Breaker?
 
 Without a circuit breaker, when a service fails:
+
 1. Every request waits for a timeout
 2. Your app becomes slow and unresponsive
 3. You waste resources on doomed requests
 4. The failing service gets overwhelmed with retry attempts
 
 With a circuit breaker:
+
 1. After detecting failures, requests fail immediately
 2. Your app stays responsive
 3. The failing service gets breathing room
@@ -40,8 +44,10 @@ With a circuit breaker:
 ```
 
 - **CLOSED**: Normal operation. Requests pass through, failures are tracked.
-- **OPEN**: Circuit tripped. Requests immediately return 503 (Service Unavailable).
-- **HALF_OPEN**: Testing recovery. Limited requests allowed to check if service recovered.
+- **OPEN**: Circuit tripped. Requests immediately return 503 (Service
+  Unavailable).
+- **HALF_OPEN**: Testing recovery. Limited requests allowed to check if service
+  recovered.
 
 ## Basic Usage
 
@@ -52,9 +58,9 @@ const provider = new FetchClientProvider();
 provider.setBaseUrl("https://api.example.com");
 
 provider.useCircuitBreaker({
-  failureThreshold: 5,    // Open after 5 failures
-  openDurationMs: 30000,  // Stay open for 30 seconds
-  successThreshold: 2,    // Close after 2 successes in HALF_OPEN
+  failureThreshold: 5, // Open after 5 failures
+  openDurationMs: 30000, // Stay open for 30 seconds
+  successThreshold: 2, // Close after 2 successes in HALF_OPEN
 });
 
 const client = provider.getFetchClient();
@@ -71,7 +77,8 @@ const response = await client.getJSON("/users");
 
 ## Per-Domain Circuit Breaker
 
-Each domain gets its own circuit breaker, so one failing service doesn't affect others:
+Each domain gets its own circuit breaker, so one failing service doesn't affect
+others:
 
 ```ts
 provider.usePerDomainCircuitBreaker({
@@ -89,13 +96,13 @@ await client.getJSON("https://api2.example.com/data"); // Circuit for api2
 ```ts
 provider.useCircuitBreaker({
   // When to open the circuit
-  failureThreshold: 5,      // Number of failures before opening (default: 5)
-  failureWindowMs: 60000,   // Time window for counting failures (default: 60000)
+  failureThreshold: 5, // Number of failures before opening (default: 5)
+  failureWindowMs: 60000, // Time window for counting failures (default: 60000)
 
   // Recovery
-  openDurationMs: 30000,    // Time to stay OPEN before testing (default: 30000)
-  successThreshold: 2,      // Successes needed to close circuit (default: 2)
-  halfOpenMaxAttempts: 1,   // Max concurrent test requests (default: 1)
+  openDurationMs: 30000, // Time to stay OPEN before testing (default: 30000)
+  successThreshold: 2, // Successes needed to close circuit (default: 2)
+  halfOpenMaxAttempts: 1, // Max concurrent test requests (default: 1)
 
   // What counts as failure
   isFailure: (response) => response.status >= 500,
@@ -105,6 +112,7 @@ provider.useCircuitBreaker({
 ## What Counts as a Failure?
 
 By default, these are treated as failures:
+
 - HTTP 5xx responses (server errors)
 - HTTP 429 responses (rate limited)
 - Network errors (connection refused, timeout, etc.)
@@ -213,7 +221,9 @@ const failures = breaker.getFailureCount("https://api.example.com/users");
 const timeSinceOpen = breaker.getTimeSinceOpen("https://api.example.com/users");
 
 // Time until HALF_OPEN
-const timeUntilHalfOpen = breaker.getTimeUntilHalfOpen("https://api.example.com/users");
+const timeUntilHalfOpen = breaker.getTimeUntilHalfOpen(
+  "https://api.example.com/users",
+);
 ```
 
 ## Combined with Rate Limiting
@@ -224,16 +234,17 @@ Use both patterns together:
 // Rate limiter prevents overwhelming healthy APIs
 provider.useRateLimit({
   maxRequests: 100,
-  windowSeconds: 60
+  windowSeconds: 60,
 });
 
 // Circuit breaker stops requests to failing APIs
 provider.useCircuitBreaker({
-  failureThreshold: 5
+  failureThreshold: 5,
 });
 ```
 
-**Order matters**: Rate limiting happens first. If you're rate limited, the request never reaches the circuit breaker.
+**Order matters**: Rate limiting happens first. If you're rate limited, the
+request never reaches the circuit breaker.
 
 ## Removing Circuit Breaker
 
@@ -245,9 +256,9 @@ provider.removeCircuitBreaker();
 
 ```ts
 import {
-  FetchClientProvider,
   CircuitOpenError,
-  RateLimitError
+  FetchClientProvider,
+  RateLimitError,
 } from "@foundatiofx/fetchclient";
 
 const provider = new FetchClientProvider();
@@ -290,14 +301,15 @@ async function fetchUser(id: string) {
 
 ## Circuit Breaker vs Rate Limiting
 
-| Aspect | Rate Limiter | Circuit Breaker |
-|--------|--------------|-----------------|
-| **Purpose** | Prevent overloading API | Prevent cascading failures |
-| **Trigger** | Request count exceeds limit | Failure count exceeds threshold |
-| **When** | Before request | After response |
-| **Blocks** | Excess requests | All requests to failing service |
+| Aspect       | Rate Limiter                | Circuit Breaker                           |
+| ------------ | --------------------------- | ----------------------------------------- |
+| **Purpose**  | Prevent overloading API     | Prevent cascading failures                |
+| **Trigger**  | Request count exceeds limit | Failure count exceeds threshold           |
+| **When**     | Before request              | After response                            |
+| **Blocks**   | Excess requests             | All requests to failing service           |
 | **Recovery** | Automatic after time window | State machine (OPEN → HALF_OPEN → CLOSED) |
 
 Use both together for maximum resilience:
+
 - Rate limiter keeps you within API limits
 - Circuit breaker handles when things go wrong

docs/guide/configuration.md

@@ -1,10 +1,14 @@
 # Configuration
 
-FetchClient uses a **default provider** behind the scenes that manages shared configuration, cache, and state for your entire app. You don't need to create or manage providers directly - just call the configuration functions and everything works.
+FetchClient uses a **default provider** behind the scenes that manages shared
+configuration, cache, and state for your entire app. You don't need to create or
+manage providers directly - just call the configuration functions and everything
+works.
 
 ## How It Works
 
-When you use `new FetchClient()` or call functions like `getJSON()`, they all share the same default provider. This means:
+When you use `new FetchClient()` or call functions like `getJSON()`, they all
+share the same default provider. This means:
 
 - **Shared configuration** - Set `baseUrl` once, use it everywhere
 - **Shared cache** - Cache entries are available to all clients
@@ -18,8 +22,8 @@ setBaseUrl("https://api.example.com");
 
 // Both use the same configuration and cache
 const client = new FetchClient();
-await client.getJSON("/users");  // Uses baseUrl
-await getJSON("/users");         // Same baseUrl, same cache
+await client.getJSON("/users"); // Uses baseUrl
+await getJSON("/users"); // Same baseUrl, same cache
 ```
 
 ## Basic Setup
@@ -237,7 +241,12 @@ getCurrentProvider().loading.on((isLoading) => {
 
 ```ts
 // user-service.ts
-import { deleteJSON, getCache, getJSON, postJSON } from "@foundatiofx/fetchclient";
+import {
+  deleteJSON,
+  getCache,
+  getJSON,
+  postJSON,
+} from "@foundatiofx/fetchclient";
 
 export async function getUsers() {
   const { data } = await getJSON<User[]>("/users", {
@@ -262,4 +271,7 @@ export async function deleteUser(id: number) {
 
 ## Advanced: Custom Providers
 
-For advanced use cases like connecting to multiple APIs with different configurations, you can create separate `FetchClientProvider` instances. See the [API reference](https://jsr.io/@foundatiofx/fetchclient/doc/~/FetchClientProvider) for details.
+For advanced use cases like connecting to multiple APIs with different
+configurations, you can create separate `FetchClientProvider` instances. See the
+[API reference](https://jsr.io/@foundatiofx/fetchclient/doc/~/FetchClientProvider)
+for details.

docs/guide/error-handling.md

@@ -1,6 +1,7 @@
 # Error Handling
 
-FetchClient provides flexible error handling with support for expected status codes, custom error callbacks, and RFC 7807 Problem Details.
+FetchClient provides flexible error handling with support for expected status
+codes, custom error callbacks, and RFC 7807 Problem Details.
 
 ## Default Behavior
 
@@ -93,23 +94,23 @@ const response = await client.postJSON("/api/users", {
 });
 
 if (!response.ok) {
-  console.log(response.problem.title);   // "Validation Error"
-  console.log(response.problem.detail);  // "The request was invalid"
-  console.log(response.problem.status);  // 400
-  console.log(response.problem.errors);  // { email: ["Invalid email format"] }
+  console.log(response.problem.title); // "Validation Error"
+  console.log(response.problem.detail); // "The request was invalid"
+  console.log(response.problem.status); // 400
+  console.log(response.problem.errors); // { email: ["Invalid email format"] }
 }
 ```
 
 ### Problem Details Structure
 
 ```ts
 interface ProblemDetails {
-  type?: string;      // URI identifying the problem type
-  title?: string;     // Short human-readable summary
-  status?: number;    // HTTP status code
-  detail?: string;    // Detailed explanation
-  instance?: string;  // URI identifying this occurrence
-  errors?: Record<string, string[]>;  // Field-level errors
+  type?: string; // URI identifying the problem type
+  title?: string; // Short human-readable summary
+  status?: number; // HTTP status code
+  detail?: string; // Detailed explanation
+  instance?: string; // URI identifying this occurrence
+  errors?: Record<string, string[]>; // Field-level errors
 }
 ```
 
@@ -134,7 +135,7 @@ problem.errors = {
 Validate request data before sending:
 
 ```ts
-import { setModelValidator, ProblemDetails } from "@foundatiofx/fetchclient";
+import { ProblemDetails, setModelValidator } from "@foundatiofx/fetchclient";
 
 setModelValidator(async (data) => {
   if (!data) return null;
@@ -170,7 +171,7 @@ if (!response.ok) {
 
 ```ts
 import { z } from "zod";
-import { setModelValidator, ProblemDetails } from "@foundatiofx/fetchclient";
+import { ProblemDetails, setModelValidator } from "@foundatiofx/fetchclient";
 
 const UserSchema = z.object({
   email: z.string().email("Invalid email format"),
@@ -275,9 +276,9 @@ try {
 
 ```ts
 import {
+  CircuitOpenError,
   FetchClient,
   FetchClientProvider,
-  CircuitOpenError,
   RateLimitError,
 } from "@foundatiofx/fetchclient";
 
@@ -290,7 +291,7 @@ const client = provider.getFetchClient();
 
 async function apiRequest<T>(
   url: string,
-  options?: RequestOptions
+  options?: RequestOptions,
 ): Promise<{ data: T | null; error: string | null }> {
   try {
     const response = await client.getJSON<T>(url, {
@@ -307,7 +308,7 @@ async function apiRequest<T>(
       case 400:
         return {
           data: null,
-          error: response.problem.detail || "Invalid request"
+          error: response.problem.detail || "Invalid request",
         };
       case 401:
         // Redirect to login