Yes. I added a direct resolver unit test for that case: test_module_sync_condition_matches_import_and_require now resolves the same conditional export object in both ResolutionMode::Import and ResolutionMode::Require, with module-sync and node branches, and asserts both modes select ./sync.mjs.

Re-ran:

• cargo fmt --check
• cargo test -p node_resolver

Pushed a fix for the CI failures. The spec was also importing module-sync-pkg/nested, which Deno rejected as an undeclared package subpath dependency in debug spec runs. I trimmed the fixture to assert the root package import and createRequire() path; the direct resolver unit test still covers both import and require selecting module-sync.

Re-ran locally:

• cargo fmt --check
• cargo test -p node_resolver

I also attempted the filtered spec locally, but stopped it during the first full CLI test-target build after confirming the CI failure source from logs.

Pushed a follow-up fix for the debug spec failure: the local module-sync-pkg fixture now has a root package.json dependency declaration, so bare package validation accepts module-sync-pkg while still resolving from the fixture node_modules package.

Re-ran locally:

• cargo fmt --check
• cargo test -p node_resolver

I also attempted the focused spec locally, but stopped it while it was still in the first full specs_tests compile.

@divybot please open a PR in the docs repo updating relevant sections about this new export condition