Improve resolve on windows

[ahaoboy]

Description of changes

The following test fails on Windows due to the path separator

  _require(`${CWD}/fixtures/test_modules/test-uuid.js`);

Checklist

• Created unit tests in tests/unit and/or in Rust for my feature if needed
• Ran make fix to format JS and apply Clippy auto fixes
• Made sure my code didn't add any additional warnings: make check
• Added relevant type info in types/ directory
• Updated documentation if needed (API.md/README.md/Other)

[richarddavison]

We have a "to_abs_path" used by require_resolve in various places. Use that method inside of require resolve where this case isn't covered!

[nabetti1720]

@ahaoboy , Thanks for addressing this issue. I may have missed it in the recent fixes.

The results returned by require_resolve() (build-in module name, bytecode cache name, absolute path including search results from package.json, presence or absence of prefix used on the loader side, etc.) vary, so I think it's difficult to judge here.

I'll take a look at this if you don't mind. :)

[ahaoboy]

The results returned by require_resolve() (build-in module name, bytecode cache name, absolute path including search results from package.json, presence or absence of prefix used on the loader side, etc.) vary, so I think it's difficult to judge here.

I'll take a look at this if you don't mind. :)

The logic is indeed a bit complicated, and I'm not sure whether it should be handled here. If there is a better way, you can directly submit a new PR

[ahaoboy]

Strange error
https://github.com/awslabs/llrt/actions/runs/11892672367/job/33136055896

And we may also need to handle node protocols such as node:fs

[nabetti1720]

@ahaoboy , This issue was addressed in #690. We have confirmed that the Require tests pass at least in windows-build.

[nabetti1720]

@ahaoboy, #690 has been merged into mainline, so this PR is no longer needed. :)