windowsfy

Node.js package.json scripts fail on Windows CMD or PowerShell when they use inline environment variables, Unix-only commands, glob patterns, or single-quoted arguments. Scanning for these Windows-incompatible patterns identifies the exact cause.

To fix npm scripts with inline environment variables for Windows compatibility, use cross-env to set environment variables portably across CMD, PowerShell, and Unix shells. This replaces inline variable assignment patterns that fail on Windows-native shells.

The best way to handle Unix-only commands in npm scripts for cross-platform use is replacing them with shx, which provides portable shell commands. Alternatively, apply shell-specific fallbacks if your Node.js project must remain Windows-locked.

Yes, PowerShell 5.1 chaining behavior breaks Node.js npm scripts because it handles command chaining differently than Unix shells. Detecting this PowerShell 5.1 specific behavior during compatibility scanning allows for targeted shell-specific fixes.

To resolve glob pattern expansion issues in package.json scripts on Windows, use the glob package to handle file matching programmatically. Windows-native shells do not expand glob patterns like Unix shells, causing npm run commands to fail.

Yes, you can use cross-env and shx together to make Node.js build scripts fully cross-platform. cross-env handles inline environment variables while shx replaces Unix-only shell commands, ensuring scripts run correctly on Windows CMD and PowerShell.