The error makes no sense to me, it's as if it was compiled without hxnodejs right? But how could that be, when it's just JS file, it's not compiled locally or is it?
No hurry in any case. :)
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)
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.
I meant completion for the JS exported from Haxe, to be used from other JS projects.
Thanks guys.
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.
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
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.
let me check on that , thanks for the insight!
Then again drobox doesn't cover global installation dir, wherever that is.
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.
Good to know what I wanted can actually be done though, thanks!