Forum Discussion

akshays's avatar
akshays
Ace
3 years ago

Error while installing lithium-sdk on Windows 10

Running into 'Failed at the node-sass@3.13.1 postinstall script' error while trying to install lithium-sdk on Windows using - npm install -global lithium-sdk Error: ' This is a bug in `n...
  • cgrinton's avatar
    cgrinton
    3 years ago

    I'm not sure if it will address your specific issue, but I've found the following thread useful in the past for getting lithium-sdk installed on Windows: https://community.khoros.com/t5/Developer-Discussion/How-to-Install-the-Lithium-Community-SDK-on-Windows/td-p/430762

    Installation steps do seem to be very sensitive to versions of components that are used. Here are steps that have worked for me:

    choco install rsync -y
choco install nodejs-lts --version=10.24.1 -y
npm install --production windows-build-tools --vs2015
npm install -g gulp 
npm install -g lithium-sdk

     A couple of notes:

    • These steps must be run as a user with local administrator rights.
    • This was a while ago now, and versions may have changed in ways that make these steps no longer work.
cgrinton's avatar
cgrinton
Expert

I'm not sure if it will address your specific issue, but I've found the following thread useful in the past for getting lithium-sdk installed on Windows: https://community.khoros.com/t5/Developer-Discussion/How-to-Install-the-Lithium-Community-SDK-on-Windows/td-p/430762

Installation steps do seem to be very sensitive to versions of components that are used. Here are steps that have worked for me:

choco install rsync -y
choco install nodejs-lts --version=10.24.1 -y
npm install --production windows-build-tools --vs2015
npm install -g gulp 
npm install -g lithium-sdk

 A couple of notes:

  • These steps must be run as a user with local administrator rights.
  • This was a while ago now, and versions may have changed in ways that make these steps no longer work.
akshays's avatar
akshays
Ace
3 years ago

This seems to work just fine. I guess the issue was with the version that I was using. I had rsync and windows-build-tools 2015 set up already. But changed the Node version to from 11.15.0 to 10.24.1 using nvm. And, it seems like that was the original issue. Thanks a lot!