Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to specify an http proxy? #38

Open
sbley opened this issue Jun 22, 2021 · 6 comments
Open

How to specify an http proxy? #38

sbley opened this issue Jun 22, 2021 · 6 comments

Comments

@sbley
Copy link

sbley commented Jun 22, 2021

I need to operate npm-force-resolutions behind a corporate proxy. How can I specify the http proxy?

Without a proxy I get this error message:

C:\Users\sbley\AppData\Roaming\npm-cache\_npx\10760\node_modules\npm-force-resolutions\out\npm_force_resolutions\core.cljs:61
  (go
  ^
Error: Timeout trying to fetch resolutions from npm
    at switch__2144__auto__ (C:\Users\sbley\AppData\Roaming\npm-cache\_npx\10760\node_modules\npm-force-resolutions\out\npm_force_resolutions\core.cljs:61:3)
    at C:\Users\sbley\AppData\Roaming\npm-cache\_npx\10760\node_modules\npm-force-resolutions\out\npm_force_resolutions\core.cljs:61:3
    at npm_force_resolutions$core$find_resolutions_$_state_machine__2145__auto____1 (C:\Users\sbley\AppData\Roaming\npm-cache\_npx\10760\node_modules\npm-force-resol
utions\out\npm_force_resolutions\core.js:476:4)
    at cljs.core.async.impl.ioc-helpers/FN-IDX (C:\Users\sbley\AppData\Roaming\npm-cache\_npx\10760\node_modules\npm-force-resolutions\out\npm_force_resolutions\core
.js:492:85)
    at cljs.core.async.impl.ioc-helpers/run-state-machine (C:\Users\sbley\AppData\Roaming\npm-cache\_npx\10760\node_modules\npm-force-resolutions\out\cljs\core\async
\impl\ioc_helpers.cljs:35:23)
    at cljs.core.async.impl.ioc-helpers/run-state-machine-wrapped (C:\Users\sbley\AppData\Roaming\npm-cache\_npx\10760\node_modules\npm-force-resolutions\out\cljs\co
re\async\impl\ioc_helpers.cljs:39:6)
    at fret (C:\Users\sbley\AppData\Roaming\npm-cache\_npx\10760\node_modules\npm-force-resolutions\out\cljs\core\async.cljs:490:22)
    at take-cb (C:\Users\sbley\AppData\Roaming\npm-cache\_npx\10760\node_modules\npm-force-resolutions\out\cljs\core\async.cljs:188:63)
    at C:\Users\sbley\AppData\Roaming\npm-cache\_npx\10760\node_modules\npm-force-resolutions\out\cljs\core\async\impl\channels.cljs:160:45
    at Immediate.cljs$core$async$impl$dispatch$process_messages (C:\Users\sbley\AppData\Roaming\npm-cache\_npx\10760\node_modules\npm-force-resolutions\out\cljs\core
\async\impl\dispatch.cljs:18:7)
@github-user-7
Copy link

github-user-7 commented Aug 12, 2021

I also really need this. Please help! Thanks :)

I've configured npm for the proxy as described here, but it doesn't seem to make any difference for npm-force-resolutions.
https://jjasonclark.com/how-to-setup-node-behind-web-proxy/

@angusmccloud
Copy link

@github-user-7 or @sbley - Did you find a resolution?

@github-user-7
Copy link

Unfortunately no, I ended up just using a different system that isn't required to use our corporate proxy server.

@sbley
Copy link
Author

sbley commented Oct 12, 2021

No solution here :-/ I push to get rid of npm-force-resolutions in our project as soon as possible.

@angusmccloud
Copy link

Bummer... I unfortunately pulled it out of our project yesterday as well.

@Clete2
Copy link

Clete2 commented Jun 13, 2022

Need this too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants