hah yes, I think this is certainly the issue… thanks for mentioning that
it’s an edge case, but we can guard against it, I’ve just merged an update that will avoid the error in the future