fix(js): pass project Jest config for TypeScript transformation

[misrasaurabh1]

Summary

• Fixed Jest test failures on TypeScript projects by passing the project's Jest config file
• Added _find_jest_config() function to locate Jest config in project and parent directories
• Supports monorepos where Jest config is at repository root, not package root

Problem

When running codeflash on TypeScript projects like next.js, generated tests were failing with:

Jest encountered an unexpected token
Jest failed to parse a file. This happens e.g. when your code or its dependencies use non-standard JavaScript syntax, or when Jest is not configured to support such syntax.

Root Cause

The Jest test runner functions (run_jest_behavioral_tests, run_jest_benchmarking_tests, run_jest_line_profile_tests) were not passing a --config flag to Jest, causing it to run without the project's TypeScript transformation configuration.

Solution

1. Added _find_jest_config() function that:

   • Searches for common Jest config files (jest.config.ts/js/mjs/cjs/json)
   • Searches parent directories for monorepo support (up to 5 levels)
   • Stops at git root or monorepo root (package.json with workspaces)

2. Updated all three Jest runner functions to pass --config={path} when a config is found

Test plan

• Tested against next.js monorepo where jest.config.js is at repo root
• Verified Jest config is found in parent directory for packages/next

🤖 Generated with Claude Code

[Saga4]

Can add test for finding the jest config with a tmp project.