Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Apr 03 06:33
    TC218 edited #173
  • Apr 03 06:31
    TC218 edited #173
  • Mar 14 19:04
    JordanPlayz158 commented #89
  • Mar 14 09:23
    back2dos commented #89
  • Mar 14 08:21

    kevinresol on master

    Cleanup (compare)

  • Mar 14 03:40
    kevinresol commented #89
  • Mar 14 03:39
    JordanPlayz158 commented #89
  • Mar 14 01:37
    kevinresol commented #89
  • Mar 14 01:15
    AlexHaxe commented #89
  • Mar 14 00:56
    JordanPlayz158 commented #89
  • Feb 27 12:07
    cedx synchronize #172
  • Feb 24 09:05
    dependabot[bot] edited #164
  • Feb 24 09:05
    dependabot[bot] edited #164
  • Feb 24 09:05
    dependabot[bot] synchronize #164
  • Feb 24 09:05

    dependabot[bot] on npm_and_yarn

    Bump tar from 6.0.1 to 6.1.9 B… (compare)

  • Feb 24 09:05
    dependabot[bot] edited #164
  • Feb 24 09:04
    dependabot[bot] edited #164
  • Feb 24 09:04

    kevinresol on master

    15.12.0 (compare)

  • Feb 24 09:04

    kevinresol on v15.12.0

    (compare)

  • Feb 24 07:25

    kevinresol on master

    Support linux-arm64 for nightly… (compare)

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
oO
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
Juraj Kirchheim
@back2dos
hmm, seems like a precedence thing
lix formatter and lix run formatter should work for global lix
but so should haxelib run formatter
Juraj Kirchheim
@back2dos
here's a fully isolated setup: mkdir foo && cd foo && npm init -y && npm i lix && npx lix scope create && npx lix install haxelib:formatter && npx lix formatter
works for me even if I have no lix installed and whether or not I have haxe and haxelib installed globally through the normal installer .. can you try that please?
Philippe
@elsassph
Hmm ok so lix formatter works when run as a npm script, but not in the terminal.
VSCode's integrated terminal. And scoped lix. Not adding npx if that matters.
Well that matters visibly :D
Juraj Kirchheim
@back2dos
lix formatter should work if and only if you've install lix via npm i -g lix
Philippe
@elsassph
I'd have thought that a global lix running in a scoped location would figure things out...
Juraj Kirchheim
@back2dos
hmm, ordinarily it does, but as always, there's a dozen things that can go wrong
tbh, I don't even understand how you managed to get lix and nonshimmed haxelib in the same $PATH (as your output fromlix run-haxelib . formatter indicates) ... that takes a quite peculiar setup ... are you throwing npm-haxe in the mix or something? ^^
Philippe
@elsassph
Haha no it's a clean lix setup. But I may have an old static install of haxe.
Philippe
@elsassph
Got a very interesting issue in CI: I forgot lix download and when building I got
haxelib path: /root/haxe/versions/4.1.2/haxelib: error while loading shared libraries: libneko.so.2: cannot open shared object file: No such file or directory
Juraj Kirchheim
@back2dos
where's haxelib from in that case?