What problem does it solve?
Working on Node.js projects from Windows introduces hidden encoding, path, and line ending issues that break scripts, shebangs, and path access checks, leading to hard-to-debug errors that do not occur on macOS or Linux.
Core Features & Use Cases
- BOM Prevention: Guides correct PowerShell 5.1 file write methods to avoid UTF-8 BOM corruption that breaks Node.js shebangs.
- Path Case Handling: Provides case-insensitive path comparison logic to resolve mismatches between Windows case-preserving filesystems and Node.js path resolution.
- Encoding & Line Ending Fixes: Resolves CP1252 mojibake in terminal output and CRLF line ending conflicts for cross-platform shell scripts.
- Use Case: For example, when editing Node.js scripts or project configs on Windows, or when terminal output shows garbled Unicode characters, this skill provides actionable steps to avoid breakage.
Quick Start
Use the windows-dev-environment skill to fix garbled terminal output, path access errors, and BOM-related shebang breaks when working on Node.js projects from a Windows machine.