windows-compatibility

Cross-platform path handling fails on Windows due to illegal filename characters, specifically colons in timestamps, and brittle Git commands like git -C. Avoiding these characters and using portable path utilities ensures consistent behavior across Windows, macOS, and Linux.

To avoid illegal Windows characters, format timestamps for filenames by eliminating colons entirely. Apply a safe timestamp format for logs and artifacts to ensure file operations do not break on Windows systems.

The best way to handle file paths across Windows, macOS, and Linux is to normalize separators and build portable file system paths using path.join or path.resolve equivalents. This standardizes path operations across different development environments.

You should not use git -C to run commands across different operating systems because it is brittle. Prefer explicit directory changes and portable Git commands to ensure robust Git CLI usage in cross-platform codebases.

Identify and mitigate Windows-specific issues by applying guidelines that avoid illegal filename characters, standardize path operations with path.join, and eliminate confusing Git commands. This ensures robust file naming and consistent behavior across platforms.

Using path.join resolves path separator issues between Windows and Unix environments by normalizing separators automatically. It builds portable file system paths, preventing the path handling breaks common when moving code between operating systems.