I-npm iyasebenza, kodwa ukulanda kwemithombo yemvelo ye-tfjs-node kudlula i-proxy
Setha indawo ezungezile efundwa yi-scripts/resources.js, futhi uhlole ukulandelana kwesiguquli sokuqala esingenalutho ngaphambi kokushintsha ukucushwa kwe-npm futhi.
Ngendlela yokulanda ye-scripts/resources.js ku-tfjs-node, nika inqubo yengane indawo yayo ezungezile ye-proxy. Ku-PowerShell session eqala umsebenzi wephakethe:
$env:HTTPS_PROXY = 'http://proxy.example:8080'
$env:HTTP_PROXY = 'http://proxy.example:8080'Qala umsebenzi ohlosiwe kusuka kuleyo session. Ngokulanda kwemithombo yomphakathi okuvunyelwe, sebenzisa i-HTTP endpoint evela ku-uhlu lwama-proxy e-HTTP kulezi zindinganiso. I-script ifunda i-process.env ngalokhu kulandelana bese ithatha inani lokuqala elingenalutho: HTTPS_PROXY, https_proxy, HTTP_PROXY, http_proxy. Inani lakudala langaphambili lingafihla ushintsho olwenzile kamuva ohlwini.
Isicelo se-npm registry esisebenzayo sihlola omunye umlandi. Ukufakwa kwayo kwe-proxy ku-.npmrc akudingeki kunikeze isiguquli senqubo esisetshenziswa yi-script yemithombo yemvelo. Gcina i-URL ehlulekile kanye nesigaba sokulanda ukuze ukhombe ukufakwa okungekho.
Lokhu kulandelana kungokwenguqulo yomthombo ochaziwe. Kufanise nokulanda kohlelo lwe-tfjs-node olufakiwe, esikhundleni sokulungisa i-script egciniwe ngezinto ezicatshangelwayo zolunye uhlobo.