fs: can't require non-ASCII file paths in Shift-JIS filesystem

[kyranet]

Version

v22.13.0, v23.6.0

Platform

Microsoft Windows NT 10.0.26100.0 x64

Subsystem

fs

What steps will reproduce the bug?

1. Use Japanese Windows with Shift-JIS (aka CP932)
2. Load a non-ASCII file path with require such as ヘルプ.js

How often does it reproduce? Is there a required condition?

Always reproduceable under a Shift-JIS filesystem.

What is the expected behavior? Why is that the expected behavior?

The file is loaded correctly.

What do you see instead?

"Process exited with code 3221225477"

Additional information

• May be similar to fs.rmSync('速') crash without throw #56049, although it's an issue for a different method and doesn't mention the Shift-JIS requirement.
• The issue was found in bug: If a file named "ヘルプ.ts" is added to the "commands" folder, the bot fails to start. sapphiredev/pieces#460 for reference, which used require in the user's case, the aforementioned issue also links a reproducible example repository, although not a minimal one for testing purposes, the issue has been reproduced with a simple require in REPL as well.
• The same code works fine:
  • If the filesystem isn't Shift-JIS (UNIX, non-Japanese Windows).
  • ASCII names are used instead.
  • When run with an alternative runtime such as Deno.

[github-actions]

This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

[kyranet]

Not stale

[github-actions]

This issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

[github-actions]

This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.