Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Nov 07 16:58
    GlassySundew commented #138
  • Oct 22 13:44
    kevinresol commented #73
  • Oct 22 13:22
    Aidan63 opened #73
  • Oct 18 19:13
    pfoof opened #177
  • Aug 10 00:16
    pzmarzly edited #176
  • Aug 10 00:16
    pzmarzly edited #176
  • Aug 10 00:12
    pzmarzly opened #176
  • Aug 10 00:08
    pzmarzly commented #65
  • Aug 10 00:06
    pzmarzly commented #65
  • Aug 10 00:04
    pzmarzly commented #65
  • Jul 27 22:51
    player-03 commented #167
  • Jul 10 18:40
    back2dos closed #174
  • Jul 10 18:40
    back2dos commented #174
  • Jul 06 01:34
    TheDrawingCoder-Gamer closed #175
  • Jul 06 00:05
    TheDrawingCoder-Gamer commented #175
  • Jul 06 00:03
    kevinresol commented #175
  • Jul 05 23:53
    TheDrawingCoder-Gamer opened #175
  • Jul 05 23:20
    TheDrawingCoder-Gamer opened #174
  • Apr 03 06:33
    TC218 edited #173
  • Apr 03 06:31
    TC218 edited #173
Kevin Leung
@kevinresol
Can you please try again with v15.11.6?
Peter Achberger
@Antriel
Worked, thanks. :)
Gabor Varadi
@varadig
There is any solution to lock pm's version when update one of them?
grepsuzette
@grepsuzette
do you mean the lix --flat option?
Peter Achberger
@Antriel
Looking into adapting my Haxe build too to run as npm lib, inspiring myself with Lix setup. I wonder, why does Lix use ncc? Purely for minification?
Peter Achberger
@Antriel
Also, if anyone has any hints regarding actually publishing to npm I would be grateful. Planning on having main lib and bunch of smaller tools as separate libs, not sure about multi/mono repo for that, or even naming conventions. :D
Juraj Kirchheim
@back2dos
lix has a number of dependencies and there are advantages to bundling them for distribution ... 1. faster installation (only one package with tree shaken dependencies included) meaning faster CI 2. all users always get the same code 3. it doesn't break if some (possibly transitive) dependencies are removed from the registry 4. it executes faster (in part due to the minification, in part due to the fact that there are no more require calls)
Peter Achberger
@Antriel
Great points. Something to consider.
In my case the sublibraries would have relatively big npm dependencies, such as aws stuff.
So ncc is about taking the main lib, and its npm dependencies, and merging that into single js, to achieve all that?
That could be viable approach for the less monstrous dependencies that are probably gonna be used often. Just not sure if it's considered a good practice, as it won't link to the dependencies in npm, and might miss security issues and disallows users forcing newer version if they want to.
Peter Achberger
@Antriel
Any hint for achieving at least top-level JS code completion?
Juraj Kirchheim
@back2dos
completion om what? and where? ^^
Peter Achberger
@Antriel
I meant completion for the JS exported from Haxe, to be used from other JS projects.
Juraj Kirchheim
@back2dos
hmm ... I kinda expected that to work ^^
Kevin Leung
@kevinresol
genes would be more complete I suppose
Peter Achberger
@Antriel
Oh, nice. Will look at that too, though I don't think I need splitting. Then again, maybe I do. Support for real modules import { Stuff } from 'foo' could be useful.
Thanks guys.
Peter Achberger
@Antriel
Genes works out pretty well. But not when combined with ncc. I lose the types. :D
Kinda odd to mix them up I guess. On one hand I don't mind having the published files as es modules in individual files. On the other hand, the few npm dependencies I will have, I would rather bundle up.
Peter Achberger
@Antriel
Hm, I suppose I could merge the original d.ts files into a single one, and just copy it over to the ncc generated file. A bit of complex work...
Peter Achberger
@Antriel
Will just go without ncc for now I think. Also a bit odd how genes puts everything exposed at root, but I can live with that.
Kevin Leung
@kevinresol
Have you guys seen something like this before?
+ npm i -g lix
/root/.nvm/versions/node/v14.17.5/bin/haxe -> /root/.nvm/versions/node/v14.17.5/lib/node_modules/lix/bin/haxeshim.js
/root/.nvm/versions/node/v14.17.5/bin/lix -> /root/.nvm/versions/node/v14.17.5/lib/node_modules/lix/bin/lix.js
/root/.nvm/versions/node/v14.17.5/bin/haxelib -> /root/.nvm/versions/node/v14.17.5/lib/node_modules/lix/bin/haxelibshim.js
/root/.nvm/versions/node/v14.17.5/bin/neko -> /root/.nvm/versions/node/v14.17.5/lib/node_modules/lix/bin/nekoshim.js
> lix@15.12.0 postinstall /root/.nvm/versions/node/v14.17.5/lib/node_modules/lix
> node bin/postinstall.js
sh: 1: node: Permission denied
npm ERR! code ELIFECYCLE
npm ERR! syscall spawn
npm ERR! file sh
npm ERR! errno ENOENT
npm ERR! lix@15.12.0 postinstall: `node bin/postinstall.js`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the lix@15.12.0 postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2022-03-25T07_15_42_168Z-debug.log
it is on ubuntu 20.04
Peter Achberger
@Antriel
Permission denied sounds like it needs to be done with sudo or something. I'm not versed in Linux permissions system, but I would expect installing it globally for just this user should work. But I guess it depends on what permissions the postinstall.jsfile has. /shrug
Kevin Leung
@kevinresol
I suppose that ENOENT means it can't find "node"?
Peter Achberger
@Antriel
I think it can also say that if it doesn't have access. The sh: 1: node: Permission denied seems more important.
I do sometimes get ENOENT errors when dropbox interferes (locks the file it's trying to write or something), but never saw the permission denied thing.
Kevin Leung
@kevinresol
ahh right
let me check on that , thanks for the insight!
Peter Achberger
@Antriel
Or maybe I did see permission denied with dropbox too, now that I think about it. I started disabling dropbox whenever I npm i. :D
Then again drobox doesn't cover global installation dir, wherever that is.
Rudy Ges
@kLabz
Hey :) can i setup lix (or haxeshim ?) to use another folder than ~/haxe/ for its stuff ?
Rudy Ges
@kLabz
Yep with HAXESHIM_ROOT env :)
Kevin Leung
@kevinresol
yeah you got it
Peter Achberger
@Antriel
I keep pondering about best way to use git submodules for my dependencies, but can't find a solution that isn't too manual or requires additional tool. :/
I can tell Lix to use local path, but for nested dependencies that gets quite annoying.
And including another hxml in main hxml doesn't consider the relative path, apparently by design, so I can't go that route either.
Juraj Kirchheim
@back2dos
there's support for ${__dirname} in paths IIRC
Peter Achberger
@Antriel
Oh! That would work. Haxe doesn't seem to complain, but I've already went the Lix route and just used dev and manually removed the warning.
Good to know what I wanted can actually be done though, thanks!
Thomas J. Webb
@thomasjwebb

I'm getting this error while a pipeline runs lix download:

Failed to get version information from haxelib because Error: certificate has expired

How do I figure out what's causing that? It works fine for me locally.
Thomas J. Webb
@thomasjwebb
What I can see is that this is not failing when it's installing something from gitlab or github but is failing when it's installing from haxelib.
Thomas J. Webb
@thomasjwebb
lix successfully downloads neko, haxe and packages from github and gitlab. It just can't deal with haxelib... on netlify's builder. Which I just confirmed is set to the present.
Kevin Leung
@kevinresol
likely a haxelib server error
I think i saw the same thing at the same time but apparently it is fine right now
Thomas J. Webb
@thomasjwebb
Yeah I figured it might be an intermittent error but it was weird that it worked on my m achine. But not with repeated tries on netlify.
赵 冰洋
@zhaobingyang_gitlab
1