Great catch, thanks so much!! This should now be fixed in v0.5.5 (available now).
I can confirm that it's resolved with v0.5.5.
