V8 --jitless Mode Configuration for Consistent Local‑Production Execution

The goal is to guarantee that a Node.js application behaves identically when run with V8's --jitless flag in production as it does during local development, where the flag may be omitted and JIT compilation is allowed.

In local environments the V8 engine may optimize hot functions with TurboFan, while production containers that enforce --jitless force interpreter‑only execution, potentially exposing code paths that rely on JIT‑specific optimizations or on assumptions about execution speed. It is unclear which built‑in modules or native addons depend on those optimizations, and whether simple functional tests can reveal the divergence.

• Which V8 optimization flags (e.g., --turbo-fan, --trace-opt) are effectively disabled by --jitless, and how might their absence affect Node.js core modules?
• What strategies exist to statically or dynamically detect reliance on JIT‑optimized code paths before deploying with --jitless?