Trying to compile Lectrote, had an error

I downloaded node.js, and then the github lectrote package. After running npm install, I had the following error:

10082 error npm v3.10.10 10083 error code ELIFECYCLE 10084 error lectrote@1.2.8 preinstall: `if [ -f quixe/LICENSE ]; then echo Quixe already installed; elif [ -d .git ]; then git submodule init; git submodule update; else git clone https://github.com/erkyrath/quixe.git; fi` 10084 error Exit status 1 10085 error Failed at the lectrote@1.2.8 preinstall script 'if [ -f quixe/LICENSE ]; then echo Quixe already installed; elif [ -d .git ]; then git submodule init; git submodule update; else git clone https://github.com/erkyrath/quixe.git; fi'. 10085 error Make sure you have the latest version of node.js and npm installed. 10085 error If you do, this is most likely a problem with the lectrote package, 10085 error not with npm itself. 10085 error Tell the author that this fails on your system: 10085 error if [ -f quixe/LICENSE ]; then echo Quixe already installed; elif [ -d .git ]; then git submodule init; git submodule update; else git clone https://github.com/erkyrath/quixe.git; fi 10085 error You can get information on how to open an issue for this project with: 10085 error npm bugs lectrote 10085 error Or if that isn't available, you can get their info via: 10085 error npm owner ls lectrote 10085 error There is likely additional logging output above. 10086 verbose exit [ 1, true ]

I downloaded Node.js from github.com/erkyrath/lectrote.

I just realized I didn’t have git installed as requested in the readme, so I went to git-for-windows.github.io/ and downloaded and installed the windows version. I then re-ran npm install, and it stopped at the same error.

I even tried downloading quixe from github, and unzipping it into lectrote’s quixe folder (including the LICENSE file), but somehow npm install still gives the same error.

Well, I opened package.json and deleted the conditional git command since I had already downloaded quixe into its own folder. Now everything compiled, and npm start worked just fine. So it’s all fixed!

Good :slight_smile: