Hi @dev3464546822, thanks again for bringing this up! Our engineers are looking into the issue and I’ll post again once the fix is up and live.
The tl;dr of what was happen is related to how our text editor was reading the script.
At the moment - we have rolled back the feature that is causing the issue. Thanks for your patience and understanding!