Error handling bug #174
Description
Current Behavior
An error occurring during webpack building does not result in blueprint.sh returning a non-0 exit code (bash will think it succeeded)
Expected Behavior
blueprint.sh should exit with code 1 when the error is detected
Steps to Reproduce
Build the current release and check the error code
Log: https://github.com/BlueprintFramework/docker/actions/runs/19774810999/job/56665628996
Blueprint Version
beta-2025-11
Panel Version
N/A
Is there an existing issue for this?
- I have searched the existing issues before opening this issue.
- I have provided all relevant details and tested my reproduction steps.
- I have checked to my best capabilities and believe this is a bug with the software, and not a configuration issue with my specific system.
- I have made sure to check that this bug is the fault of Blueprint and is not caused by stock Pterodactyl.