ESLint migration codemod uses npx in a pnpm project

Link to the code that reproduces this issue

https://github.com/princeeze/next-codemod-pnpm-repro

To Reproduce

1. Create a Next.js 14 app with pnpm and ESLint enabled
2. Run pnpm install
3. Make sure the git working tree is clean
4. Run the codemod to migrate from next lint to the ESLint CLI:

pnpx @next/codemod@canary next-lint-to-eslint-cli . --force

Current vs. Expected behavior

Current: On a pnpm project it logs

Running "npx @eslint/migrate-config /path/to/.eslintrc.json" to convert legacy config...

Expected: I'd expect the migrate step to use pnpm (e.g. pnpm dlx @eslint/migrate-config).

Provide environment information

perating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 25.6.0: Fri Jul 31 19:18:49 PDT 2026; root:xnu-12377.161.14~5/RELEASE_ARM64_T6000
  Available memory (MB): 16384
  Available CPU cores: 8
Binaries:
  Node: 26.8.1
  npm: 11.19.0
  Yarn: N/A
  pnpm: 11.25.0
Relevant Packages:
  next: 14.2.18 // An outdated version detected (latest is 16.3.4), upgrade is highly recommended!
  eslint-config-next: 14.2.18
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.9.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)

Not sure

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

No response

Start with the next-lint-to-eslint-cli codemod entry point and reproduce the behavior using the linked pnpm project and the pnpx @next/codemod@canary next-lint-to-eslint-cli . --force command. Trace the migration step that invokes @eslint/migrate-config, then verify that the command uses the project's package-manager workflow rather than npx.