@63klabs/cache-data 1.3.6 → 1.3.8

package/{AI_CONTEXT.md → AGENTS.md}

@@ -391,14 +391,91 @@ This package is used in high-traffic Lambda functions. Performance matters.
 
 ## 5. Testing Strategy
 
-### 5.1 Test Organization
+### 5.1 Test Framework Migration
+
+**CRITICAL: Mocha to Jest Migration in Progress**
+
+This project is actively migrating from Mocha to Jest. During this transition period:
+
+**Migration Status:**
+- **Phase**: Active migration - both frameworks supported
+- **Legacy**: Mocha tests (`*-tests.mjs`) - maintain but don't create new
+- **Current**: Jest tests (`*.jest.mjs`) - all new tests must use this
+- **Goal**: Complete migration to Jest, remove Mocha dependency
+
+**File Naming Conventions:**
+- Mocha (legacy): `cache-tests.mjs`, `endpoint-tests.mjs`, `*-property-tests.mjs`
+- Jest (current): `cache-tests.jest.mjs`, `endpoint-tests.jest.mjs`, `*-property-tests.jest.mjs`
+
+**Test Execution Commands:**
+```bash
+# Run Mocha tests only (legacy)
+npm test
+
+# Run Jest tests only (current)
+npm run test:jest
+
+# Run both test suites (REQUIRED for CI/CD)
+npm run test:all
+
+# Run specific test suites
+npm run test:cache        # Mocha cache tests
+npm run test:cache:jest   # Jest cache tests
+npm run test:endpoint     # Mocha endpoint tests
+npm run test:endpoint:jest # Jest endpoint tests
+```
+
+**Migration Guidelines:**
+
+1. **Creating New Tests:**
+   - ALWAYS use Jest (`*.jest.mjs` files)
+   - Follow Jest patterns and assertions
+   - Use Jest mocking (not Sinon)
+   - Place in same directory as Mocha tests
+
+2. **Modifying Existing Tests:**
+   - If minor change: Update Mocha test
+   - If major change: Consider migrating to Jest
+   - If time permits: Migrate to Jest and delete Mocha version
+
+3. **Test Coverage:**
+   - Both test suites must pass in CI/CD
+   - Jest coverage: `coverage-jest/` directory
+   - Mocha coverage: `coverage/` directory (if generated)
+
+4. **Property-Based Tests:**
+   - Use fast-check in both Mocha and Jest
+   - Same property definitions work in both frameworks
+   - Migrate property tests to Jest when possible
+
+**Why Jest?**
+- Better ESM support
+- Built-in mocking (no Sinon needed)
+- Better async/await handling
+- More modern and actively maintained
+- Better IDE integration
+- Simpler configuration
+
+**Migration Checklist for Converting Tests:**
+- [ ] Create new `*.jest.mjs` file
+- [ ] Import from `@jest/globals` instead of `chai`
+- [ ] Change `expect().to.equal()` to `expect().toBe()`
+- [ ] Change `expect().to.not.equal()` to `expect().not.toBe()`
+- [ ] Replace Sinon mocks with Jest mocks
+- [ ] Update async test patterns if needed
+- [ ] Run Jest tests to verify: `npm run test:jest`
+- [ ] Delete old Mocha test file
+- [ ] Update any references in documentation
+
+### 5.2 Test Organization
 
 Tests mirror source structure:
 
 ```
 test/
 ├── cache/                  # Cache module tests
-│   ├── cache-tests.mjs
+│   ├── cache-tests.mjs (Mocha - legacy)
+│   ├── cache-tests.jest.mjs (Jest - new)
 │   ├── in-memory-cache/
 │   │   ├── unit/
 │   │   ├── integration/
@@ -407,6 +484,8 @@ test/
 ├── documentation/          # Documentation validation
 │   └── property/
 ├── endpoint/               # Endpoint module tests
+│   ├── endpoint-tests.mjs (Mocha - legacy)
+│   ├── endpoint-tests.jest.mjs (Jest - new)
 ├── logging/                # Logging tests
 ├── request/                # Request handling tests
 ├── response/               # Response tests
@@ -414,22 +493,72 @@ test/
 └── helpers/                # Test utilities
 ```
 
-### 5.2 Test Naming Conventions
+**Note**: During migration, both `.mjs` (Mocha) and `.jest.mjs` (Jest) files coexist in the same directories.
+
+### 5.3 Test Naming Conventions
 
+**Mocha (Legacy):**
 - Test files: `*-tests.mjs`
 - Property tests: `*-property-tests.mjs`
 - Integration tests: `*-integration-tests.mjs`
 - Unit tests: `*-unit-tests.mjs` or `*-tests.mjs`
 
-### 5.3 Test Framework
+**Jest (Current - Use for All New Tests):**
+- Test files: `*.jest.mjs`
+- Property tests: `*-property-tests.jest.mjs`
+- Integration tests: `*-integration-tests.jest.mjs`
+- Unit tests: `*-unit-tests.jest.mjs` or `*.jest.mjs`
+
+### 5.4 Test Framework
+
+**CRITICAL: Test Framework Migration in Progress**
+
+This project is currently migrating from Mocha to Jest. Both frameworks are supported during the transition period.
+
+**Current Status:**
+- **Legacy Tests**: Mocha tests (files ending in `-tests.mjs`)
+- **New Tests**: Jest tests (files ending in `.jest.mjs`)
+- **Migration Goal**: All tests will eventually be in Jest
 
-- **Test Runner**: Mocha
-- **Assertions**: Chai (expect style)
-- **Property Testing**: fast-check
-- **Mocking**: Sinon (when necessary)
-- **HTTP Testing**: chai-http
+**Test Framework by Type:**
 
-### 5.4 Writing Good Tests
+**Mocha (Legacy - Being Phased Out):**
+- Test Runner: Mocha
+- Assertions: Chai (expect style)
+- Property Testing: fast-check
+- Mocking: Sinon
+- HTTP Testing: chai-http
+- File Pattern: `*-tests.mjs`
+
+**Jest (Current - All New Tests):**
+- Test Runner: Jest
+- Assertions: Jest built-in (expect)
+- Property Testing: fast-check (same as Mocha)
+- Mocking: Jest built-in
+- HTTP Testing: Jest with mocks
+- File Pattern: `*.jest.mjs`
+
+**Rules for Test Development:**
+
+1. **ALL NEW TESTS MUST BE WRITTEN IN JEST** using the `*.jest.mjs` file pattern
+2. **DO NOT create new Mocha tests** - only maintain existing ones
+3. **When modifying existing tests**, consider migrating to Jest if time permits
+4. **Both test suites must pass** before merging (`npm run test:all`)
+5. **Jest tests coexist with Mocha tests** in the same directories
+
+**Test Execution:**
+```bash
+# Run Mocha tests (legacy)
+npm test
+
+# Run Jest tests (new)
+npm run test:jest
+
+# Run both test suites (required for CI/CD)
+npm run test:all
+```
+
+### 5.5 Writing Good Tests
 
 **DO**:
 - Test one thing per test
@@ -438,6 +567,7 @@ test/
 - Make tests deterministic
 - Keep tests fast
 - Use property-based testing for core logic
+- **Write all new tests in Jest** (not Mocha)
 
 **DON'T**:
 - Test implementation details
@@ -445,11 +575,12 @@ test/
 - Use real AWS services (mock them)
 - Make tests dependent on each other
 - Skip tests without good reason
+- **Create new Mocha tests** (migration in progress)
 
-**Example Test Structure:**
+**Example Test Structure (Jest - Use This for New Tests):**
 
 ```javascript
-import { expect } from 'chai';
+import { describe, it, expect } from '@jest/globals';
 import { Cache } from '../src/lib/dao-cache.js';
 
 describe('Cache', () => {
@@ -458,7 +589,7 @@ describe('Cache', () => {
             const conn = { host: 'example.com', path: '/api' };
             const hash1 = Cache.generateIdHash(conn);
             const hash2 = Cache.generateIdHash(conn);
-            expect(hash1).to.equal(hash2);
+            expect(hash1).toBe(hash2);
         });
 
         it('should generate different hashes for different inputs', () => {
@@ -466,11 +597,29 @@ describe('Cache', () => {
             const conn2 = { host: 'example.com', path: '/api2' };
             const hash1 = Cache.generateIdHash(conn1);
             const hash2 = Cache.generateIdHash(conn2);
-            expect(hash1).to.not.equal(hash2);
+            expect(hash1).not.toBe(hash2);
         });
 
         it('should handle null input gracefully', () => {
-            expect(() => Cache.generateIdHash(null)).to.not.throw();
+            expect(() => Cache.generateIdHash(null)).not.toThrow();
+        });
+    });
+});
+```
+
+**Legacy Test Structure (Mocha - Maintain Only, Don't Create New):**
+
+```javascript
+import { expect } from 'chai';
+import { Cache } from '../src/lib/dao-cache.js';
+
+describe('Cache', () => {
+    describe('generateIdHash()', () => {
+        it('should generate consistent hash for same input', () => {
+            const conn = { host: 'example.com', path: '/api' };
+            const hash1 = Cache.generateIdHash(conn);
+            const hash2 = Cache.generateIdHash(conn);
+            expect(hash1).to.equal(hash2);
         });
     });
 });

package/CHANGELOG.md

@@ -2,13 +2,86 @@
 
 All notable changes to this project will be documented in this file.
 
-Proposed and upcoming changes may be found on [63Klabs/cache-data Issues](https://github.com/63Klabs/cache-data/issues).
+> **Note:** This project is still in beta. While every effort is made to prevent breaking changes, they may still occur. If after upgrading to a new version you experience any issue, please report the issue and go back to a previous version until a fix is released.
+
+To report an issue, or to see proposed and upcoming enhancements, check out [63Klabs/cache-data Issues](https://github.com/63Klabs/cache-data/issues) page on GitHub.
 
 Report all vulnerabilities under the [Security menu](https://github.com/63Klabs/cache-data/security/advisories) in the Cache-Data GitHub repository.
 
-## v1.3.7 (unreleased)
+## v1.3.8 (2026-03-02)
+
+### Security
+- **Updated the way dependencies are listed reduce npm Security Vulnerabilities** [Spec: 1-3-8-npm-security-vulnerabilities-fix](.kiro/specs/1-3-8-npm-security-vulnerabilities-fix/)
+  - Fixed 1 low, 20 high, and 1 critical severity vulnerabilities in development dependencies
+  - Updated devDependencies to specific secure versions:
+    - `@aws-sdk/client-dynamodb`, `@aws-sdk/client-s3`, `@aws-sdk/client-ssm`, `@aws-sdk/lib-dynamodb`: Updated from `3.x` to `^3.995.0`
+    - `mocha`: Updated from `^11.x` to `^11.7.5`
+    - `chai`: Updated from `^6.x` to `^6.2.2`
+    - `chai-http`: Updated from `^5.x` to `^5.1.2`
+    - `sinon`: Updated from `^21.x` to `^21.0.1`
+    - `fast-check`: Updated from `^4.x` to `^4.5.3`
+  - Added npm overrides for transitive dependencies:
+    - `diff`: `>=8.0.3` (fixes low severity DoS vulnerability)
+    - `minimatch`: `>=10.2.2` (fixes high severity ReDoS vulnerability)
+    - `glob`: `>=13.0.6` (fixes transitive vulnerabilities)
+  - No breaking changes to public APIs
+  - All existing tests pass
+  - Production dependencies remain secure (0 vulnerabilities)
+
+### Added
+- **APIRequest Pagination, Retry, and X-Ray Enhancements** [Spec: 1-3-8-api-request-pagination-retries-xray](.kiro/specs/1-3-8-api-request-pagination-retries-xray/) addresses [#171](https://github.com/63Klabs/cache-data/issues/171), [#172](https://github.com/63Klabs/cache-data/issues/172), [#173](https://github.com/63Klabs/cache-data/issues/173)
+  - **Automatic Pagination**: APIRequest now supports automatic pagination for APIs that return paginated results
+    - Configurable pagination labels for different API response structures
+    - Batch processing for concurrent page requests
+    - Support for both offset-based and token-based pagination
+    - Automatic result combination into single response
+    - Pagination metadata in response (total pages, total items, incomplete status)
+  - **Automatic Retry Logic**: APIRequest now includes built-in retry functionality for transient failures
+    - Configurable retry attempts (default: 1 retry after initial attempt)
+    - Automatic retry on network errors, empty responses, parse errors, and 5xx status codes
+    - Optional retry on 4xx status codes (disabled by default)
+    - Retry metadata in response (attempts made, final attempt number)
+  - **Enhanced X-Ray Subsegments**: Improved AWS X-Ray tracing for better observability
+    - Unique subsegment names for each request using timestamps
+    - Retry and pagination metadata included in X-Ray traces
+    - Separate subsegments for each paginated request
+    - Detailed annotations and metadata for debugging
+  - **Response Metadata**: New optional metadata field in responses
+    - Retry information (occurred, attempts, final attempt)
+    - Pagination information (occurred, total pages, total items, incomplete status)
+    - Only present when retries or pagination occur
+  - **Backwards Compatibility Maintained**: All new features are opt-in via configuration
+    - Existing code continues to work without modification
+    - No breaking changes to public API
+    - Default behavior unchanged when new features not configured
+  - See documentation: [Pagination Guide](docs/features/tools/api-request-pagination.md), [Retry Guide](docs/features/tools/api-request-retry.md), [X-Ray Guide](docs/features/tools/api-request-xray.md)
+- **tools.AppConfig** replaces `tools._ConfigSuperClass` and receives an `.init()` to simplify initialization
+  - Updated documentation to reflect how `Config` can be implemented to extend `tools._ConfigSuperClass`
+  - Instead of separate `Response.init()`, `ClientRequest.init()` and `Connections.init()` a single `AppConfig.init()` can be used within the `Config.init()`
+
+### Enhancement
 
-- Next release
+- **Expanded Generic Responses** - Additional responses for status codes
+  - Added responses for 408, 418, and 427
+  - Ensured all generic responses have the same statuses
+- **Revised Documentation** - Clarified and revised documentation
+  - Reviewed all code examples
+  - Reviewed implementation instructions
+
+## v1.3.7 (2026-02-06)
+
+### Fixed
+- **Cache DAO Undefined Header Bug** [Spec: 1-3-7-cache-dao-fix](.kiro/specs/1-3-7-cache-dao-fix/) - Fixed production bug where undefined values were passed to HTTP headers, causing request failures with "Invalid value 'undefined' for header" errors
+  - Cache.getHeader() now normalizes undefined to null for consistent behavior
+  - Added defensive validation at header assignment points in CacheableDataAccess.getData()
+  - Added Cache._isValidHeaderValue() helper method for header validation
+  - **Most likely cause:** The move from over-use of JSON Stringify/parse cycles in favor of cloning in v1.3.6. JSON stringify/parse removed undefined values from objects, covering an underlying issue that is now fixed.
+
+### Added
+- **Jest Testing Framework** [Spec: 1-3-7-cache-dao-fix](.kiro/specs/1-3-7-cache-dao-fix/) - Set up Jest alongside Mocha for better AWS integration testing
+  - Configured Jest with ES module support
+  - Added npm scripts: `test:jest`, `test:all`, `test:cache:jest`
+  - Jest tests use `*.jest.mjs` pattern to avoid conflicts with Mocha tests
 
 ## v1.3.6 (2025-02-02)
 

package/CONTRIBUTING.md

@@ -12,6 +12,24 @@ Submit feature requests. To keep this project simple and maintainable we accept
 
 After you have successfully participated in the bug reporting and feature request process, fork the repository and make your changes in a separate branch. Once you're satisfied with your changes, submit a pull request for review. Please only submit small changes (a single feature) at first. Pull requests with major code updates or frequent pull requests will often get ignored. Changes should also have code and testing methods well documented.
 
+All code changes MUST start as an Issue (or security report) with a clear description of the problem or enhancement. No changes should be submitted to the repository without an attached, and approved, Issue.
+
+Code developed (by AI or Human) outside of Kiro (see below) must NOT be submitted directly to the repository. Instead submit a proof of concept for a new piece of code or method via the Issue tracker as an enhancement. Someone from the team will review, evaluate the usefulness, and then implement using the proper process.
+
+## Use of AI
+
+This project utilizes the Spec-Driven, AI-Assisted Engineering approach.
+
+Spec-Driven, AI-Assisted Engineering (SD-AI) is a software development methodology that prioritizes creating detailed, structured specifications before writing code. It priortizes context, requirements, and architectural constraints to generate accurate, non-hallucinated code. This approach shifts from ad-hoc, prompt-driven "vibe coding" to a structured, human-guided, AI-executed workflow, improving reliability in complex projects.
+
+> Contributors are responsible for every line of code--AI-generated or not.
+
+Code must be reviewed, understood, and tested by a human before being merged.
+
+Kiro is the required AI coding assistant for final integrations, documentation, and testing, as it is in the AWS Ecosystem and this project is deveoped to deploy on the AWS platform. Just like test suites, Kiro ensures the proper tests, documentation, and guardrails are in place. Kiro is as important as commit-hooks and tests as it is a tool that ensures quality checks and should not be bypassed.
+
+Ensure [AGENTS](./AGENTS.md) and Kiro steering documents are reviewed, understood, and used by both humans and AI.
+
 ## Development Setup
 
 Tests and documentation are critical to this project.
@@ -138,24 +156,11 @@ All public APIs must have complete JSDoc documentation. See [Documentation Stand
  */
 ```
 
-## Use of AI
-
-This project utilizes the Spec-Driven, AI-Assisted Engineering approach.
-
-Spec-Driven, AI-Assisted Engineering (SD-AI) is a software development methodology that prioritizes creating detailed, structured specifications before writing code. It priortizes context, requirements, and architectural constraints to generate accurate, non-hallucinated code. This approach shifts from ad-hoc, prompt-driven "vibe coding" to a structured, human-guided, AI-executed workflow, improving reliability in complex projects.
-
-> Contributors are responsible for every line of code--AI-generated or not.
-
-Code must be reviewed, understood, and tested by a human before being merged.
-
-Kiro is the preferred AI coding assistant as it is in the AWS Ecosystem and this project is deveoped to deploy on the AWS platform. Ensure [AI Context](./AI_CONTEXT.md) and [Kiro steering documents](.kiro/steering/ai-context-reference.md) are reviewed, understood, and used by both humans and AI. 
-
 ## Current Contributors
 
 Thank you to the following people who have contributed to this project:
 
 Chad Kluck\
 DevOps & Developer Experience Engineer\
-AWS Certified Cloud Practitioner | AWS Certified Developer - Associate | AWS
-Certified Solutions Architect - Associate\
+AWS Certified Developer and Solutions Architect\
 [Website](https://chadkluck.me)

package/README.md

@@ -29,7 +29,10 @@ The @63klabs/cache-data package provides three main modules:
 - **Cache Profiles**: Configure multiple cache profiles with different expiration policies
 
 ### Endpoint Module
-- **HTTP/HTTPS Requests**: Make requests to external APIs and endpoints with built-in retry logic
+- **HTTP/HTTPS Requests**: Make requests to external APIs and endpoints with automatic pagination, retry logic, and X-Ray tracing
+- **Automatic Pagination**: Fetch all pages from paginated APIs automatically with configurable batch processing
+- **Automatic Retry**: Retry failed requests with configurable conditions (network errors, server errors, empty responses)
+- **Enhanced X-Ray Tracing**: Detailed monitoring and debugging with AWS X-Ray subsegments
 - **Connection Management**: Define and manage multiple endpoint connections with authentication
 - **Request Caching**: Automatically cache endpoint responses to reduce API calls and improve performance
 - **Flexible Configuration**: Support for custom headers, query parameters, request bodies, and timeouts
@@ -136,6 +139,42 @@ console.log("API Response:", response.body);
 console.log("Status Code:", response.statusCode);
 ```
 
+### Using APIRequest with Pagination and Retry
+
+```javascript
+const { tools } = require("@63klabs/cache-data");
+
+// Make a request with automatic pagination and retry
+const request = new tools.APIRequest({
+  host: "api.example.com",
+  path: "/users",
+  parameters: {
+    limit: 100  // Items per page
+  },
+  pagination: {
+    enabled: true  // Automatically fetch all pages
+  },
+  retry: {
+    enabled: true,
+    maxRetries: 2  // Retry failed requests up to 2 times
+  }
+});
+
+const response = await request.send();
+
+// Response contains all users from all pages
+const allUsers = JSON.parse(response.body).items;
+console.log(`Retrieved ${allUsers.length} total users`);
+
+// Check metadata
+if (response.metadata?.pagination?.occurred) {
+  console.log(`Fetched ${response.metadata.pagination.totalPages} pages`);
+}
+if (response.metadata?.retries?.occurred) {
+  console.log(`Succeeded after ${response.metadata.retries.attempts} attempts`);
+}
+```
+
 ### Using Utility Tools
 
 ```javascript
@@ -198,8 +237,8 @@ This will install dependencies, configure the pre-commit hook for documentation
 
 ## AI Context
 
-See [AI_CONTEXT.md](AI_CONTEXT.md) for important context and guidelines for AI-generated code in this repository.
+See [AGENTS.md](AGENTS.md) for important context and guidelines for AI-generated code in this repository.
 
 The context file is also helpful (and perhaps essential) for HUMANS developing within the application's structured platform as well.
 
-AI Assisted Engineering of this solution was provided by [Kiro](https://kiro.dev/). Steering documents are provided in the repository's [.kiro](.kiro/steering/ai-context-reference.md) directory. Because testing is tightly coupled with the implementation, it is suggested all documents, code, and tests are thoroughly reviewed before, and updated after, any changes.
+AI Assisted Engineering of this solution was provided by [Kiro](https://kiro.dev/). Steering documents are provided in the repository's `.kiro/steering/` directory. Because testing is tightly coupled with the implementation, it is suggested all documents, code, and tests are thoroughly reviewed before, and updated after, any changes.

package/eslint.config.js

@@ -0,0 +1,53 @@
+import js from '@eslint/js';
+
+export default [
+	js.configs.recommended,
+	{
+		languageOptions: {
+			ecmaVersion: 'latest',
+			sourceType: 'module',
+			globals: {
+				// Node.js globals
+				console: 'readonly',
+				process: 'readonly',
+				Buffer: 'readonly',
+				__dirname: 'readonly',
+				__filename: 'readonly',
+				exports: 'writable',
+				module: 'writable',
+				require: 'readonly',
+				global: 'readonly',
+				// Mocha globals
+				describe: 'readonly',
+				it: 'readonly',
+				before: 'readonly',
+				after: 'readonly',
+				beforeEach: 'readonly',
+				afterEach: 'readonly',
+				// ES2021 globals
+				globalThis: 'readonly'
+			}
+		},
+		rules: {
+			'no-template-curly-in-string': 'error',
+			'no-eval': 'error',
+			'no-implied-eval': 'error',
+			'no-new-func': 'error'
+		}
+	},
+	{
+		files: ['test/**/*.mjs', 'test/**/*.js', 'scripts/**/*.mjs', 'scripts/**/*.js', 'src/**/*.js'],
+		rules: {
+			'no-restricted-imports': ['error', {
+				patterns: [{
+					group: ['child_process'],
+					importNames: ['exec', 'execSync'],
+					message: 'Use execFile or execFileSync instead of exec/execSync to prevent shell injection. See .kiro/steering/secure-coding-practices.md'
+				}]
+			}]
+		}
+	},
+	{
+		ignores: ['node_modules/**', 'coverage/**', 'coverage-jest/**', '.git/**']
+	}
+];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@63klabs/cache-data",
-  "version": "1.3.6",
+  "version": "1.3.8",
   "description": "Cache data from an API endpoint or application process using AWS S3 and DynamoDb",
   "author": "Chad Leigh Kluck (https://chadkluck.me)",
   "license": "MIT",
@@ -21,28 +21,43 @@
     "object-hash": "^3.0.0"
   },
   "devDependencies": {
-    "@aws-sdk/client-dynamodb": "3.x",
-    "@aws-sdk/client-s3": "3.x",
-    "@aws-sdk/client-ssm": "3.x",
-    "@aws-sdk/lib-dynamodb": "3.x",
-    "chai": "^6.x",
-    "chai-http": "^5.x",
-    "fast-check": "^4.x",
-    "mocha": "^11.x",
-    "sinon": "^21.x"
+    "@aws-sdk/client-dynamodb": "^3.995.0",
+    "@aws-sdk/client-s3": "^3.995.0",
+    "@aws-sdk/client-ssm": "^3.995.0",
+    "@aws-sdk/lib-dynamodb": "^3.995.0",
+    "@eslint/js": "^10.0.1",
+    "chai": "^6.2.2",
+    "chai-http": "^5.1.2",
+    "eslint": "^10.0.1",
+    "fast-check": "^4.5.3",
+    "jest": "^30.2.0",
+    "mocha": "^11.7.5",
+    "sinon": "^21.0.1"
   },
   "overrides": {
-    "fast-xml-parser": ">=5.3.4"
+    "fast-xml-parser": ">=5.3.4",
+    "diff": ">=8.0.3",
+    "minimatch": ">=10.2.2",
+    "glob": ">=13.0.6"
   },
   "scripts": {
-    "test": "mocha 'test/**/*-tests.mjs'",
+    "test": "mocha 'test/**/*-tests.mjs' --exclude 'test/migration/property/test-execution-equivalence-property-tests.mjs'",
+    "test:jest": "node --experimental-vm-modules node_modules/jest/bin/jest.js",
+    "test:all": "npm test && npm run test:jest",
+    "test:migration:validation": "mocha test/migration/property/test-execution-equivalence-property-tests.mjs",
     "test:cache": "mocha 'test/cache/**/*-tests.mjs'",
+    "test:cache:jest": "node --experimental-vm-modules node_modules/jest/bin/jest.js test/cache",
     "test:config": "mocha 'test/config/**/*-tests.mjs'",
     "test:endpoint": "mocha 'test/endpoint/**/*-tests.mjs'",
+    "test:endpoint:jest": "node --experimental-vm-modules node_modules/jest/bin/jest.js test/endpoint",
+    "test:tools:jest": "node --experimental-vm-modules node_modules/jest/bin/jest.js test/tools",
     "test:logging": "mocha 'test/logging/**/*-tests.mjs'",
     "test:request": "mocha 'test/request/**/*-tests.mjs'",
     "test:response": "mocha 'test/response/**/*-tests.mjs'",
-    "test:utils": "mocha 'test/utils/**/*-tests.mjs'"
+    "test:utils": "mocha 'test/utils/**/*-tests.mjs'",
+    "lint": "eslint .",
+    "lint:fix": "eslint . --fix",
+    "lint:ci": "eslint . --max-warnings 0"
   },
   "keywords": [
     "api",