compat: tracking issue for running find-up test case

[kt3k]

This issue is part of #12886

This issue tracks the remaining issue for running the test cases of find-up in node-compat mode.

• ava (test runner) doesn't work.
  • It depends on fs.access node: add fs.access std#1684
  • It also depends on inspector, which is missing in std/node feat(node): add mock inspector module std#1688
  • It also depends on url.parse, which is missing in std/node node: add url.parse std#1666
  • fs.Stats is missing node: add fs.Stats class std#1689
  • child_process.fork is missing node: add child_process.fork std#1690

ref #12577

[bartlomieju]

Getting inspector polyfilled will be a rather involved effort, as we don't have any runtime APIs exposing inspector functionalities. @kt3k could you check which APIs from that module are actually required?

[kt3k]

inspector is used in ava. ref: https://github.com/avajs/ava/blob/main/lib/cli.js#L119-L121

But if inspector.url() returns undefined, it seems that ava is not going to use the actual inspector features

[bartlomieju]

@kt3k maybe we could shim it for now and always return undefined?

[kt3k]

ava@latest seems needing ipc features (process.send(), process.on("message") ) to communicate with forked child_processes in which the actual test cases are running.. 😬

[kt3k]

IPC BoardcastChannel is not available yet #10750

[kt3k]

find-up now seems working and I can run nps command in node compat mode without an issue. (I don't know what exactly fixed the issue, but the issue doesn't reproduce now). Closing

[bartlomieju]

ava@latest seems needing ipc features (process.send(), process.on("message") ) to communicate with forked child_processes in which the actual test cases are running.. 😬

Seems directly related to #12879

[kt3k]

Yeah, exactly. Let's track on that issue

I feel IPC features are widely used in npm ecosystem. So I think we need somehow to support it until v0