If the screen is not on, it's not "alarming" all the time. Sometimes it does, and everything is ok. Sometimes not, and the watch goes crazy until the alarm is actually displayed. Pressing buttons was ineffective: the watch did respond to BTN3 long press, but the screen was erased about after a second (backlight still on). The watch was unusable until the actual alarm is displayed (I guess that was at the start of the next minute?)
Setting the alarm to the current minute pretty reliably reproduces that weird behaviour: save the new alarm setting, go to the main watch face, and after about a second nothing is displayed and no buzzing.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
Thanks for the fixes!
The Alarm app itself: there is some weirdness: