I confirm the problem. This will be fixed in an update - I think the fix is safe as it most likely won't break existing code.