file` don't work consistently across different operating systems, particularly Windows, which can cause CI/CD pipelines to fail."> file` don't work consistently across different operating systems, particularly Windows, which can cause CI/CD pipelines to fail."> Use cross-platform commands - Awesome Reviewers file` don't work consistently across different operating systems, particularly Windows, which can cause CI/CD pipelines to fail.">
Back to all reviewers

Use cross-platform commands

prettier/prettier
Based on 2 comments
Markdown

When writing CI/CD scripts and documentation, prefer Node.js APIs over shell commands for file operations to ensure cross-platform compatibility. Shell commands like `echo "content" > file` don't work consistently across different operating systems, particularly Windows, which can cause CI/CD pipelines to fail.

CI/CD Markdown

Reviewer Prompt

When writing CI/CD scripts and documentation, prefer Node.js APIs over shell commands for file operations to ensure cross-platform compatibility. Shell commands like echo "content" > file don’t work consistently across different operating systems, particularly Windows, which can cause CI/CD pipelines to fail.

Instead of using shell-specific commands, use Node.js built-in APIs that work uniformly across all platforms:

# Avoid - doesn't work on Windows
echo "npx lint-staged" > .husky/pre-commit

# Prefer - works on all platforms
node --eval "fs.writeFileSync('.husky/pre-commit','npx lint-staged\n')"

This approach ensures that setup scripts, pre-commit hooks, and other CI/CD automation work reliably regardless of the operating system where they’re executed, reducing platform-specific failures and improving the developer experience across diverse development environments.

2
Comments Analyzed
Markdown
Primary Language
CI/CD
Category

Source Discussions