kevinresol on master
haxelib-lock.json. I was wondering what is the opinion of the group :)
lixand the way it can still evolve or by a future
haxe+haxelib+haxecoverhaul, is my question I guess. Could haxe evolve to facilitate the work of lix and similar tools instead of replacing them all?
And absolutely no idea what he meant by
This is WIP , please discuss there and don't edit directly ;)
It's not like we can discuss on a wiki page. :D Probably meant discuss here.
haxe_librariesand really dislike how npm does it.
lix install git:https://gitlab.com/org/repo#develop, apparently it can resolve the branch's head but somehow unable to switch to it
downloading git:https://gitlab.com/org/repo.git#57a30275b9362746a7aa161140e877e69c6445d6 From https://gitlab.com/org/repo * branch HEAD -> FETCH_HEAD fatal: reference is not a tree: 57a30275b9362746a7aa161140e877e69c6445d6
npm lix install haxelib:lime.
npx lix run lime
Error: Could not find haxelib "lime", does it need to be installed? Failed to invoke `haxelib run-dir lime C:\Users\473387\AppData\Roaming/haxe/haxe_libraries/lime/7.8.0/haxelib` because Error: Command failed: haxelib run-dir lime C:\Users\473387\AppData\Roaming/haxe/haxe_libraries/lime/7.8.0/haxelib.