fix: use find-up-simple to workaround ERR_PACKAGE_PATH_NOT_EXPORTED - #6342

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 63.35%. Comparing base (6728030) to head (b021ff4).
⚠️ Report is 1 commits behind head on main.

@@            Coverage Diff             @@
##             main    #6342      +/-   ##
==========================================
+ Coverage   63.30%   63.35%   +0.04%     
==========================================
  Files          64       64              
  Lines        4963     4969       +6     
  Branches     1124     1101      -23     
==========================================
+ Hits         3142     3148       +6     
  Misses       1821     1821              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

@copilot Incorporate the tests suggested in #6345

• ✅ login: mark-wiemer / name: Mark Wiemer (33df265, 64a17ba, 65994b6, 89bc53d, ade0dc7, eef944d, f2a1ff7)
• ❌ - login: @Copilot / name: copilot-swe-agent[bot]. The commit (b021ff4, e6dcbe2, f0490c1) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

@copilot use GPT-5.6 Terra, think deeply, and create a test that would fail on main but pass on this branch that uses something very similar --import=tsx. Report in a comment which tests came closest. We want to be able to catch issues like the backing one with automated tests.

@copilot Incorporate the tests suggested in #6345

Implemented in e6dcbe2.
Added the requested tests in test/node-unit/cli/config.spec.cjs for:

• config filename search order
• stopping after first found match
• returning undefined when no config is found

Also validated with npm run -s test-node-run -- test/node-unit/cli/config.spec.cjs.

@copilot use GPT-5.6 Terra, think deeply, and create a test that would fail on main but pass on this branch that uses something very similar --import=tsx. Report in a comment which tests came close...

Done in f0490c1.

Added a regression test in test/integration/options/node-flags.spec.cjs plus import-hook fixture test/integration/fixtures/options/node-flags/import-break-find-up.mjs. It uses --node-option import=... to simulate the --import=tsx-style startup resolution failure path and verifies Mocha still runs tests.

Closest existing tests I found were:

• test/integration/options/reporter-option.spec.cjs (node-option + respawn + config flow)
• test/integration/options/node-flags.spec.cjs (node-option forwarding)
• test/integration/esm.spec.cjs (loader/module-resolution error assertions)
• test/node-unit/cli/{config.spec.cjs,options.spec.js} (config/package discovery paths)

@copilot failing on windows consistently

@copilot failing on windows consistently

Fixed in b021ff4.

I checked the failing Windows CI logs (Tests run 35098596052, integration jobs) and the failure was ERR_UNSUPPORTED_ESM_URL_SCHEME from --node-option import=D:\....

I updated the test to pass a file:// URL via pathToFileURL(...).href and increased the test timeout to 5s for startup variance.

While this is a win, it is unfortunate that the months of discussion around switching to empathic have seemingly been ignored here.

find-up-simple offers nothing over it and just causes ecosystem fragmentation. exactly why we were trying to switch to empathic instead - the library everyone else uses.

would you be open to switching it? we shouldn't use downloads as a stat by itself, but ~23M vs ~9M shows you why this is a strange decision.

here you go:
main...43081j:mocha:jg/empathic-again