It caused issues when the same variable was using for requires multiple times, which caused the binding to be removed by one of the requires. There was protection against someone defining a variable that was a commoner package identifier, but that isn't really needed.
It caused issues when the same variable was using for requires multiple times, which caused the binding to be removed by one of the requires. There was protection against someone defining a variable that was a commoner package identifier, but that isn't really needed.
@tessalt
Fixes #40