When you want to clone a repository on someone else's github, the system does not let you move and prompts you that the firewall prohibits access to git://. In this case, you can only access the repository using https://.

Third, when you install npm, if you download dependencies from git, it is easy to report the following errors:

 silly pacote range manifest for regenerator-runtime@^0.10.5 fetched in 1ms silly resolveWithNewModule  regenerator-runtime@0.10.5   checking installable status silly fetchPackageMetaData error for  eve@git ://github.com/adobe-webplatform/eve.git#eef80ed Error while executing: silly fetchPackageMetaData D:\Program Files\Git\cmd\git.EXE ls-remote -h -t  git://github.com/adobe-webplatform/eve.git silly fetchPackageMetaData Silly fetchPackageMetaData false: unable to look up github.com (port 9418) silly fetchPackageMetaData silly fetchPackageMetaData exited with error code: 128

So we set Github and use https://to replace git://

The operation is as follows:
git config --global url."https://".insteadOf git://

If it still fails, continue to clear the cache:
npm cache clear

After one operation, one line of parameter settings will be added to your. gitconfig:

 [url "https://"]    insteadOf = git://

After setting, whether you clone on the terminal, use git://, or http://to access someone else's repository, the two methods will become http://by default to connect and work normally.