Cabal (terminal) fails to start: ERR_INVALID_ARG_TYPE (v12 node) about cabal-cli

[decentral1se]

Thank you @cblgh, npm install -g [email protected] worked! I'm in.

[sorenpeter]

Also getting the same error on MacOS BigSur

[cblgh]

@sorenpeter @decentral1se thanks for the issue! looks like one of our deps did something unexpected in a patch they released a while back. ironically it hasn't been caught by devs because that dep is pinned by package-lock.json which npm ignores when installing via npm install lol.

can y'all try this prepatch release i made to see if it fixes the issue for y'all?

npm -i g [email protected]

i could replicate the issue and the solution in 14.1.4-0 fixed it for me, keen to hear if that's broadly the case for others :)

[ralphtheninja]

@cblgh You mean a package-lock.json in a dependency to cabal-cli?

[cblgh]

@ralphtheninja i mean a published version of cabal-cli will not have package-lock.json be used to determine which dependncies are downloaded whe running the command npm install --global afaiu

in our case, the culprit causing issues appears to have been emilbayes/noise-protocol@2891a1f i.e. [email protected] has cabal working as intended (which appears to be the case when cloning cabal-cli and installing with npm i inside the repo folder) while having [email protected] installed (as seems to be the case when running npm i -g cabal) causes the issue mentioned in the original post

[ralphtheninja]

n our case, the culprit causing issues appears to have been emilbayes/noise-protocol@2891a1f i.e. [email protected] has cabal working as intended (which appears to be the case when cloning cabal-cli and installing with npm i inside the repo folder) while having [email protected] installed (as seems to be the case when running npm i -g cabal) causes the issue mentioned in the original post

Ah makes sense. Maybe we should remove package-lock.json completely? This way a dev or someone using the cli application directly from source will notice problems earlier. Also a bit unfortunate that a new patch version of noise-protocol broke this.