The current installation instructions mention that several external tools such as gum, timer, arduino-cli, and optionally homebrew are needed for aci to work properly. However, if one of these prerequisites (specifically gum or timer) is not installed, the script doesn’t provide a clear error or guidance on how to install them before proceeding.
This leads to confusing failures during installation, especially for first-time users who are unfamiliar with terminal UI dependencies.
🔍 Steps to Reproduce
Clone the repository:
git clone https://github.com/Vaishnav-Sabari-Girish/arduino-cli-interactive.git
Ensure one or more prerequisites are not installed (e.g., gum or timer).
Run the installer script as documented:
cd arduino-cli-interactive
chmod +x main.sh
./main.sh
Observe that installation fails without a clear message explaining the missing dependency.
❗ Expected Behavior
When a prerequisite is missing:
The script should clearly state which dependency is missing.
It should suggest how to install it (e.g., brew / package manager commands).
Ideally, the script should detect the environment (macOS/Linux) and guide accordingly.
🤔 Actual Behavior
The installer proceeds but fails without a helpful error or suggestion, leaving users confused about what’s missing.
✅ Suggested Fix
Add a dependency check at the start of the installation script that:
Verifies whether gum, timer, and arduino-cli are available in PATH.
Prints a clear message for each missing tool.
Provides installation instructions based on the OS (e.g., brew install gum timer).
💡 This will make the onboarding experience much smoother for new users and avoid frustration or abandonment.
The current installation instructions mention that several external tools such as gum, timer, arduino-cli, and optionally homebrew are needed for aci to work properly. However, if one of these prerequisites (specifically gum or timer) is not installed, the script doesn’t provide a clear error or guidance on how to install them before proceeding.
This leads to confusing failures during installation, especially for first-time users who are unfamiliar with terminal UI dependencies.
🔍 Steps to Reproduce
Clone the repository:
git clone https://github.com/Vaishnav-Sabari-Girish/arduino-cli-interactive.git
Ensure one or more prerequisites are not installed (e.g., gum or timer).
Run the installer script as documented:
cd arduino-cli-interactive
chmod +x main.sh
./main.sh
Observe that installation fails without a clear message explaining the missing dependency.
❗ Expected Behavior
When a prerequisite is missing:
The script should clearly state which dependency is missing.
It should suggest how to install it (e.g., brew / package manager commands).
Ideally, the script should detect the environment (macOS/Linux) and guide accordingly.
🤔 Actual Behavior
The installer proceeds but fails without a helpful error or suggestion, leaving users confused about what’s missing.
✅ Suggested Fix
Add a dependency check at the start of the installation script that:
Verifies whether gum, timer, and arduino-cli are available in PATH.
Prints a clear message for each missing tool.
Provides installation instructions based on the OS (e.g., brew install gum timer).
💡 This will make the onboarding experience much smoother for new users and avoid frustration or abandonment.