#ci 4 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 syntax check under PowerShell 7 proves nothing about 5.1gotchas / powershellThe parser belongs to the engine hosting it; ternary/??/&& pass in 7 and are parse errors in 5.1, and #Requires never warns you at authoring time
• 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…
• Jest's 5-second default timeout fails render tests under load, and the timed-out test breaks the next onegotchas / toolingThe first jsdom + React test of a suite pays for the cold module load; on a busy build machine it passes 5 s, Jest abandons it while its async render keeps running, and the following test fails with "button not found"…