Node-sass: npmconf is a deprecated and unmaintained dependency

[yannickcr]

node-sass is using npmconf but this package is now deprecated and unmaintained.

Therefore some npmconf issue like npm/npmconf#61 makes node-sass impossible to install in some environments.

It would be great if the npmconf dependency could be removed/replaced.

[xzyfer]

Querying what the alternative is now. npmconf is rather important to our internals and cannot simply be removed without an alternative.

[xzyfer]

run npm get proxy and npm get https-proxy as child processes. If that feels kind of clunky and heavyweight, I agree, but that's the most robust way to do it.
https://github.com/npm/npmconf/pull/61#issuecomment-169523714

[xzyfer]

As per https://github.com/npm/npmconf/pull/61#issuecomment-170880758

We'll like pull just the proxy code from npmconf into node-sass core.

[adamreisnz]

Is this an issues that is going to be addressed still? I'm getting this warning for all my installs now:

npm WARN deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm

[xzyfer]

We won't be changing this is the near future. Warnings can be ignored.
On Feb 20, 2016 9:12 PM, "Adam Buczynski" [email protected] wrote:

Is this an issues that is going to be addressed still? I'm getting this
warning for all my installs now:

npm WARN deprecated [email protected]: this package has been reintegrated into npm and is now out of date with respect to npm

—
Reply to this email directly or view it on GitHub
https://github.com/sass/node-sass/issues/1333#issuecomment-186563569.

[adamreisnz]

I know they can be ignored, but they ain't pretty. Is there no other way to do the thing that npmconf does? Or perhaps just take the lib and embed it within node-sass?

[danez]

You could simply replace the npmconf call with Environment variables. All configurations from npm are added to process.env if run in the context of npm.

PhantomJS fixed it that way.
https://github.com/Medium/phantomjs/commit/2620fb283439181cab0a99b89fdf4532455bc35d#diff-f16acefe4b6553580c43edab685f50f3L168

https://docs.npmjs.com/misc/scripts#configuration

[xzyfer]

This patch was reverted in v3.5.2 because it was not functionally equivalent and broke installations for some proxy users.

[jorrit]

In which cases did it not work?

[xzyfer]

Not 100% sure but we got many reports of installations failing behind proxies.

https://github.com/sass/node-sass/issues/1458

[xzyfer]

I noticed once case that wasn't counted for was the .npmrc config file. Could be related.