Comment by stymaar

Do you prompt it to behave this way or what?

Because here's the king of CoT I get:

> Hmm, but there's a subtlety: does babel-jest + preset-typescript transform the file to CJS by default? No — babel-jest doesn't transform ESM imports to CJS unless @babel/preset-env is configured with modules: commonjs. Without preset-env, import statements stay as ESM in the output, and Jest's CJS runtime would fail with "Cannot use import statement outside a module" unless the project is ESM and running with --experimental-vm-modules.

> Hmm wait, actually babel-preset-jest... does it include preset-env? Let me recall: babel-preset-jest = { plugins: [require('babel-plugin-jest-hoist')] } plus istanbul for coverage. No preset-env. So ESM imports stay as-is.

> But wait — if the user's project is ESM (which it probably is, given the .ts extension imports — Node's type stripping requires ESM-style? no, type stripping also works for CJS-style .ts files with require... actually, --experimental-strip-types supports both CJS and ESM .ts files. But explicit .ts extensions in imports only work in ESM mode (CJS require doesn't allow extensions... actually, does Node 22+ allow require of .ts with flag?

Lots of “but wait” and and full sentences, nothing caveman-like or extremely short sentences without verbs like the GPT thinking trace above.

(this is with unsloth's Qwen3.8-27B-UD-Q5_K_XL.gguf with T° = 0.8)