forcedotcom / lwc-dev-server-feedback

LWC Local Development
BSD 3-Clause "New" or "Revised" License
45 stars 10 forks source link

ESOCKETTIMEDOUT on LWC Server Install #51

Open mad-magic opened 4 years ago

mad-magic commented 4 years ago

After the v48.0 launch and issues surrounding LWC, #8 #47, I tried updating but ran into the connection issue.

I finally found a solution to the "There appears to be trouble with your network connection. Retrying..."

I ran "sfdx plugins:install @salesforce/lwc-dev-server -v" (for the additional verbose logging)

[2/4] Fetching packages...
verbose 31.74 Performing "GET" request to "https://registry.yarnpkg.com/@salesforce/lwc-dev-server-dependencies/-/lwc-dev-server-dependencies-1.0.53.tgz".
info There appears to be trouble with your network connection. Retrying...
verbose 80.616 Performing "GET" request to "https://registry.yarnpkg.com/@salesforce/lwc-dev-server-dependencies/-/lwc-dev-server-dependencies-1.0.53.tgz".
info There appears to be trouble with your network connection. Retrying...
verbose 186.508 Performing "GET" request to "https://registry.yarnpkg.com/@salesforce/lwc-dev-server-dependencies/-/lwc-dev-server-dependencies-1.0.53.tgz".
info There appears to be trouble with your network connection. Retrying...
verbose 296.824 Performing "GET" request to "https://registry.yarnpkg.com/@salesforce/lwc-dev-server-dependencies/-/lwc-dev-server-dependencies-1.0.53.tgz".

In order to fix this I found this: https://stackoverflow.com/questions/55845756/esockettimedout-error-while-yarn-install-command

  1. Go to "C:\Users\\AppData\Local\sfdx\client\\node-modules\yarn\lib\cli.js"
  2. Edit the "cli.js" file (as of CLI version 7.43.1)
  3. Change "timeout" in line 141290 to "600000" and Save
  4. Run "sfdx plugins:install @salesforce/lwc-dev-server"

Your mileage may vary, but I hope this helps anyone having issues.

stale[bot] commented 4 years ago

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.

TWood-IRL commented 4 years ago

Thanks @mad-magic

This had also helped me to install Another additional thing I did was navigating to

C:\Users\USER\AppData\Local\sfdx

Then deleting yarn.lock.lock folder And another yarn lock file

I finally was able to complete the installation :)

stale[bot] commented 4 years ago

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.

git2gus[bot] commented 4 years ago

This issue has been linked to a new work item: W-7431025

sanchita2017 commented 4 years ago

Thanks @mad-magic .After trying this for several hours it finally solved my issue.

stale[bot] commented 4 years ago

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.

Anks1856 commented 4 years ago

hey , in node_modules no file name as yarn Instad of in sfdx have yarn folder .... and yarn folder there is no folder name as lib/cli.js

stale[bot] commented 4 years ago

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.

git2gus[bot] commented 4 years ago

This issue has been linked to a new work item: W-7685401

Anks1856 commented 4 years ago

i have solution of this problem ====>https://www.youtube.com/watch?v=YFVVFHbTznY

stale[bot] commented 4 years ago

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.

mad-magic commented 4 years ago

In light of the latest API version update from 48.0 to 49.0, I ran into some of the same update / installation issues.

Thanks @Anks1856 for linking your solution. That shed some light on how I was able to fix the issues I found during my delete and reinstall of the Salesforce CLI (version sfdx-cli 7.63.0):

Additionally, if you run into the lock error due to previous installation attempts, as seen in #19, then I was able to correct it by deleting the folder(s) that failed during copying:

YMMV

stale[bot] commented 4 years ago

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.

satyajarag commented 3 years ago

Thanks @mad-magic , it worked for me as well.

stale[bot] commented 3 years ago

This issue has been automatically marked as type:bug-p3 because it has not had recent activity.