Update setup-project.js

[Pterjudin]

The refactor improves performance and maintainability by introducing centralized functions for repeated logic, such as execInProjectDir, and replacing synchronous file operations with asynchronous ones to prevent blocking. It enhances reliability with file existence checks (fs.pathExists) and robust error handling via try-catch. Cross-platform compatibility is ensured through consistent use of path.join, while clear and user-friendly logging with consola provides better execution feedback. Modularized, readable functions and standardized JSON formatting make the code easier to maintain and debug, resulting in a cleaner, more efficient, and user-friendly script.

What does this do?

This refactor optimizes the script for better performance, maintainability, and reliability. It centralizes repetitive logic, transitions to asynchronous file operations to prevent blocking, and incorporates robust error handling. The code also ensures cross-platform compatibility, improves user feedback through clear logging, and enhances readability by modularizing functions and maintaining consistent JSON formatting. These changes collectively result in a cleaner and more efficient script that's easier to debug and use.

Why did you do this?

The changes were made to address issues of code duplication, maintainability, and potential blocking caused by synchronous operations. Transitioning to asynchronous methods improves performance, especially in larger or concurrent setups. Introducing error handling and file existence checks prevents runtime crashes, making the script more reliable. Enhancing modularity and logging ensures that the codebase is developer-friendly and easier to debug, all while adhering to best practices for modern JavaScript development.

Who/what does this impact?

This impacts developers and downstream systems relying on the script. By improving performance and reliability, it benefits developers working on the project, making onboarding and maintenance easier. Downstream systems that depend on the script’s output will experience fewer issues caused by runtime errors or blocking operations. Any team members involved in debugging or extending the script should be informed of these updates for consistency.

How did you test this?

The changes were tested by running the script against multiple sample project setups to ensure all operations, such as removing files, updating configurations, and initializing Git, worked as expected. Asynchronous operations were verified to complete without errors or blocking, and edge cases, such as missing files or directories, were tested to ensure proper handling. Additionally, logs were reviewed for clarity and accuracy, and cross-platform compatibility was validated on Windows, macOS, and Linux systems.

[netlify]

✅ Deploy Preview for obytes-starter canceled.

Name	Link
🔨 Latest commit	bad84c1
🔍 Latest deploy log	https://app.netlify.com/sites/obytes-starter/deploys/6764b3754b799100080d332c