Clojurians Log v2

yes it looks like "unsafe-perm" didn't fix the sudo problem with global npm installation (like pointed out above)

attenzione: this command will succeed

sudo npm install -g lumo-cljs --unsafe-perm true 

We're getting lumo download errors on CI maybe 20% of the time

That's on Circle CI

should I be able to use the posix-getopt parser in lumo?

(def parser (new go/BasicParser "la" argv 2))
(parser.getopt)
Cannot read property 'gop_optind' of null

Oh not a lumo problem I guess, this works:

(.getopt parser)

@richiardiandrea btw Lumo ships posix-getopt

oh

good to know 😉

or does it

hrm

maybe it’s not accessible anymore

I see it in `js.cljs` cli.js

I know

we use it

but it’s probably hidden behind an IIFE wrapper at runtime so not accessible

kk

@richiardiandrea yeah, see https://github.com/anmonteiro/lumo/blob/master/scripts/build.js#L98-L100

I did that to prevent things from being accessible from the global scope

anyway, if you’re looking for posix-getopt examples, feel free to check https://github.com/anmonteiro/lumo/blob/master/src/js/cli.js

ok thanks, that's a big opt string 😄 I was looking at https://github.com/anmonteiro/lumo/issues/235

and was wondering if I could pick that up

the problem I see is that if we want that to work the script needs to be evaluated

definitely, should be fairly easy to tackle

also see https://github.com/mfikes/planck/commit/df609b182eb823dad4c531a3f16fe51f8847c598

what do you mean “the script needs to be evaluated”

yep, I also digged into https://github.com/anmonteiro/lumo/blob/2fc9e82c6ba4116e0312687a1d6c3cfa27a91ba5/src/js/cljs.js#L435

yes I think I need an else there that calls the same run-main-cli-fn: https://github.com/mfikes/planck/commit/df609b182eb823dad4c531a3f16fe51f8847c598#diff-13fa1297261809d0414872aca47177beR997

trigger an eval basically from the else

would it be a good approach?