Lix/Lobby

kro13

@kro13

i'm really grateful for you having time for this. thank you! i'll upgrade my global haxe later today to see if it works as expected, but unfortunately i'll have to roll it back after, so solving this issue would still be great

kro13

@kro13

seems that my previous assumptions were completely wrong. the only way i was able to make lix lime run as expected was to uninstall haxe globally and install lix globally. installing lix locally did not work anyway

kro13

@kro13

i'm afraid to be annoying, but are there any known issues with lix+nme? as one of my projects requires nme, and running it fails for me like this

λ lix nme
The binary nme.ndll is not distrubuted with source code, and is not built for your system yet.
Would you like to build it now Y/n ? >y
Update nme-dev...
nme-dev is up to date
Build binaries...
Failed to invoke `haxelib run-dir nme C:\Users\473387\AppData\Roaming/haxe/haxe_libraries/nme/6.0.58/haxelib` because Error: Command failed: haxelib run-dir nme C:\Users\473387\AppData\Roaming/haxe/haxe_libraries/nme/6.0.58/haxelib

Kevin Leung

@kevinresol

Probably because lime will invoke haxelib ( not npx haxelib)

Maybe that's why you need a global lix

Ben

@benmerckx

Anyone experienced haxelib run-dir travix ... run node => Failed to call neko because Error: spawnSync neko ENOENT before? Having some trouble running travix on newly installed windows. Global neko seems to work fine through global lix.

Thomas J. Webb

@thomasjwebb

Is there a way around this issue that doesn't involve modifying the system it's running on?
HaxeFoundation/dox#270

(related to which neko shows up in node_modules when you use npm to install lix)

Juraj Kirchheim

@back2dos

hmm, the easiest solution is to delete the neko binary installed by lix

Thomas J. Webb

@thomasjwebb

In node_modules/.bin?

That just makes it fall back to the system version, which is also old. Shouldn't lix install the right version? I don't want to have to rely on the system having neko installed on it.

Juraj Kirchheim

@back2dos

nah, the thing is that I've never really cared much about versioning neko

because it was already pronounced dead

so lix download neko when its missing ... but if it's there in the old version (2.2) then it doesn't mind

Thomas J. Webb

@thomasjwebb

Yeah I wish dox wasn't still using it. But I was already tempted to just iterate over the api xml and generate html myself...

Juraj Kirchheim

@back2dos

so you need to delete the current one ... on linux/mac it should be ~/haxe/neko and on windows %appdata%\haxe\neko

Thomas J. Webb

@thomasjwebb

I downloaded the system one and the one in node_modules

I mean, deleted

Juraj Kirchheim

@back2dos

node_modules/.bin/neko is just a shell script

it'll launch something like node node_modules/lix/bin/nekoshim.js and that thing actually runs the neko executable

Thomas J. Webb

@thomasjwebb

ah so this ironically probably will work right on netlify just it wasn't on my computer because there already was a global neko.

It's still not the right version. I have no neko in my path but it's finding the old one somehow

Juraj Kirchheim

@back2dos

magic

Thomas J. Webb

@thomasjwebb

sPoOoOoKy

Juraj Kirchheim

@back2dos

haxe --run resolve-args ${HAXE_LIBCACHE} should point you to a sub-directory of where lix puts its stuff

from there it's ../neko

Thomas J. Webb

@thomasjwebb

that gives me empty line

Juraj Kirchheim

@back2dos

ok, what OS are you on? ^^

Thomas J. Webb

@thomasjwebb

macos

Juraj Kirchheim

@back2dos

and do you have ~/haxe/neko?

Thomas J. Webb

@thomasjwebb

I do. Ah mac uses zsh now that could be the issue..

I mean for the blank line not neko being old

Juraj Kirchheim

@back2dos

ah ... right ^^

Thomas J. Webb

@thomasjwebb

Yup escaping the curly braces worked

Juraj Kirchheim

@back2dos

yeah ... haha ... I hate operating systems ...

ok, well then just delete ~/haxe/neko and that should make lix pull a fresh version

Thomas J. Webb

@thomasjwebb

yeah I keep forgetting that. zsh is actually pretty powerful but it's like not truly compatible with bash.

bam it's downloading

Juraj Kirchheim

@back2dos

I hope it's the right version now :D

Thomas J. Webb

@thomasjwebb

Yeah that fixed it. Thanks! So this shouldn't be an issue on deploy servers and such since they don't have this already there crap baggage

Juraj Kirchheim

@back2dos

but I think I bumped it almost two years ago ^^

yeah, normally only early adopters should be facing this problem on their machines ... only the cool kids!

Thomas J. Webb

@thomasjwebb

Yeah I installed lix globally more recently than that on this machine, but it's possible I accidentally let it install an old haxe version even though I've been using 4 since it was in rc stage

Philippe

@elsassph

Oh hi, I'm trying to do haxelib run formatter ... with lix but fail miserably

Juraj Kirchheim

@back2dos

hmm, formatter 1.11.0 + lix 15.9.0 seem to work just fine for me

can you illustrate your misery any further? ^^

Philippe

@elsassph

I must not understand how to map haxelib run formatter ... to lix.

Closest to something which almost works is lix run-haxelib . formatter ... which fails with

Unknown command run-dir
Haxe Library Manager 3.3.0 ...

I have latest lix / latest haxe as far as I can tell

Where communities thrive

People

Repo info

Activity