consider:
haxelib git libA <libA url>
haxelib git libB <libA url>
If libA depends on libB, it will now infinitely query the dependencies of libB (since it refers to itself indirectly).
One solution that doesn't create inflexibility is a configurable maximum depth for the dependency tree, in order to catch this easier. Other options (like checking the haxelib.json content name vs the haxelib name) might work as well.
consider:
haxelib git libA <libA url>haxelib git libB <libA url>If libA depends on libB, it will now infinitely query the dependencies of libB (since it refers to itself indirectly).
One solution that doesn't create inflexibility is a configurable maximum depth for the dependency tree, in order to catch this easier. Other options (like checking the haxelib.json content name vs the haxelib name) might work as well.