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)

Kevin Leung
@kevinresol
yes it will be saved in the hxml
so ssh+git is preferred
Gabriel Hayes
@piboistudios
How ironic ;) I was just asking my brother earlier why ever bother with SSH git
grepsuzette
@grepsuzette
ssh git is awesome, if it's your server I think it's the natural solution. But it's only for private projects of course
Kevin Leung
@kevinresol
same for gitlab/github private repos.
Kevin Leung
@kevinresol
when using the git: protocol, what is the syntax to select a branch?
trying 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
Kevin Leung
@kevinresol
ok apparently lix downloaded the files via http zip, then try to git checkout that commit.
however the correct first step should be a git fetch instead
Juraj Kirchheim
@back2dos
oO
kro13
@kro13
hello. i've installed lime via lix, using
npm lix install haxelib:lime.
trying to run it with npx lix run lime
but get an error
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.
could anyone please explain what am i doing wrong?
npx haxelib install lime works, but i'd love to use the power of lix downloadlater, which obviously will not work
grepsuzette
@grepsuzette
@kro13 I don't know the syntax with npm or npx, or how to use lime.
FWIW personally I use lix directly, e.g. lix scope create, lix install haxelib:xxx, lix --help, lix run yyy.
Kevin Leung
@kevinresol
Which lix version?
Juraj Kirchheim
@back2dos
the following works (prints the lime ASCII-art): mkdir limetest && cd limetest && npm init -y && npm i lix && npx lix scope create && npx lix install haxelib:lime && npx lix lime
kro13
@kro13
thank you for your replies. @back2dos those commands do not work for me with the same error (. probably something with my setup then. @kevinresol lix version is 15.9.0, node version is 10.15.2, OS windows 10, if it matters.
Kevin Leung
@kevinresol
the versions look fine. so yeah probably a setup issue
kro13
@kro13
here is what i've managed to figure out. first of all my global haxe is 3.4.7 which comes with haxelib 3.3.0, which seems to be incapable of performing run-dir. when i use npx haxelib run-dir lime C:\Users\473387\AppData\Roaming\haxe\haxe_libraries\lime\7.8.0\haxelib directly from terminal it uses scoped haxelib 4.0.2 and works fine. however changing @run directive in haxe_libraries\lime.xml does not work and still fails with
Failed to invoke `npx haxelib run-dir lime C:\Users\473387\AppData\Roaming\haxe\haxe_libraries\lime\7.8.0\haxelib
it seems to be running out of scope or something like that. maybe anyone could bring some light here, knowing all above?
kro13
@kro13
updating global haxe is not a desireable option right now(
Juraj Kirchheim
@back2dos
hmm ... seems like the %PATH% set by npx is lost somewhere and then it falls back to your global installation
this may take a while ^^
haxelib run-dir is actually a lix feature anyway ^^
ok, I guess I'll have to uninstall my global lix to see if this reproduces
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
oO