fix: cross-platform compatibility for build scripts

[sanjayr-12]

Description:

This PR resolves an issue with the build scripts that were not functioning properly on Windows due to the use of Unix-specific commands (mkdir -p and rm -rf). The following changes were made to ensure the build works seamlessly across both Unix and Windows environments:

• Replaced the mkdir -p command with the mkdirp package for cross-platform directory creation.
• Replaced the rm -rf command with the rimraf package for cross-platform directory removal.
• Created a moveFiles.js script to handle moving build directories (React and Next.js) and cleaning up temporary directories (distreact and distnextjs)

Error Faced:

When executing npm install or the build script in Windows Command Prompt, the following errors occurred:

• rm is not recognized as an internal or external command,
  When executing npm install or the build script on bash, the following errors occurred:
• A subdirectory or file -p already exists. Error occurred while processing: -p.
• A subdirectory or file dist already exists. Error occurred while processing: dist.

Changes:

• Updated the package.json build scripts to use mkdirp for directory creation and rimraf for directory removal.
• Added the moveFiles.js script to encapsulate the logic for moving directories and cleaning up.

Testing:

• Manually tested the build and directory operations on both cmd and bash to confirm functionality.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
convex-auth-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 25, 2024 8:44am

[thomasballinger]

Hi @sanjayr-12, are you actively developing with this on Windows? We're open to changes like this coming from contributors who work on Windows without using a bash shell and would find this convenient but we'd want these to be maintained; we need someone contributing actively to know this will keep working. Or we need a Windows CI task to check this works.

[sanjayr-12]

Hi @sanjayr-12, are you actively developing with this on Windows? We're open to changes like this coming from contributors who work on Windows without using a bash shell and would find this convenient but we'd want these to be maintained; we need someone contributing actively to know this will keep working. Or we need a Windows CI task to check this works.

Hi @thomasballinger, Yes, I work on Windows using Command Prompt and PowerShell, so I ran into these issues and fixed them. I don’t have experience setting up a Windows CI task yet, but I’m open to learning or working with others to get it done. I’m happy to help test and keep these changes working on Windows.