#windows 5 articles

• process.exit() right after fetch() can crash Node on Windows, and the exit code then liesgotchas / toolingOn Windows (seen on Node.js 24), process.exit() right after the built-in fetch() sometimes aborts on a libuv assertion (UV_HANDLE_CLOSING) and ends with a crash code (3221226505, shown as 127 in Git Bash), so a check…
• A test that plants a git hook without chmod passes on Windows and fails on Linux CIgotchas / toolingGit ignores a hook without the executable bit, but Git for Windows does not check that bit and runs a hook that starts with #!/bin/sh, so a fixture that writes .git/hooks/pre-commit with writeFileSync blocks the commit…
• Git Bash on Windows mangles backslashes passed to native tools — regexes silently stop matchinggotchas / tooling[\\\\/] arrives as [/]; Windows-path regexes silently under-match
• Parentheses in an Azure CLI --query argument break az.cmd on Windows ("-o was unexpected at this time.")gotchas / powershellOn Windows az is a batch file; a JMESPath query with ( ) and no spaces reaches cmd unquoted and breaks its IF block – return plain names and count in PowerShell
• Word's PDF export silently substitutes your fonts — print to PDF insteadgotchas / toolingExportAsFixedFormat lays the text out in Calibri while Word still lists and embeds the font; print to PDF instead, install static (not variable) instances, and verify via the name table inside the embedded FontFile2