Add build scripts for windows and linux

[Mourtz]

Important

Add build scripts build.ps1 for Windows and build.sh for Unix/Linux to automate project building and cleaning.

• Scripts:
  • Add build.ps1 for Windows using PowerShell.
  • Add build.sh for Unix/Linux using Bash.
• Functionality:
  • Both scripts create a dist directory if it doesn't exist.
  • Build bundle.js using browserify and index.html using pug.
  • Provide build, clean, and help commands.
• Error Handling:
  • Exit with error if browserify or pug is not found.
  • Display success or error messages for each build step.

^{This description was created by for bc3869c. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to bc3869c in 1 minute and 52 seconds. Click for details.

• Reviewed 169 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 3 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. visualization/scripts/build.ps1:18

• Draft comment:
  Consider wrapping external command calls (e.g., browserify and pug) in try/catch blocks for more robust error handling.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

2. visualization/scripts/build.sh:63

• Draft comment:
  Normalize the input command (e.g., using 'tr' to convert to lower-case) so that the case of the command argument is ignored, similar to the PowerShell implementation.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% While case-insensitive command matching could be user-friendly, it's not a critical issue. Build scripts typically expect exact command matches, and the help message shows the exact commands to use. The suggestion is a nice-to-have but not essential improvement. There's no evidence of user confusion or problems with the current approach. The suggestion could improve user experience by being more forgiving of capitalization. Unix commands are traditionally case-sensitive, so this deviates from convention. The benefit is minor and the current behavior follows Unix conventions. The help message clearly shows the expected commands. This comment should be removed as it suggests a non-essential change that deviates from Unix conventions without strong justification.

3. visualization/scripts/build.sh:21

• Draft comment:
  Although 'set -e' ensures the script exits on errors, consider explicitly checking and reporting exit statuses for commands like browserify and pug to provide clearer feedback, aligning with the PowerShell script's approach.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

Workflow ID: wflow_f4GsoF3Z1JoCIQtx

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}