--userconfig

[brianreavis]

After digging, this behavior is already possible by just using --config instead of --userconfig because of this line of rc (used by registry-url). Should this difference be noted in the readme, or for the sake of parity should this be brought up as an issue on rc?

[rstacruz]

neat, why not!

[rstacruz]

wait, what's --userconfig?

from how I understand what you said, it means we can use pnpm install --config custom_npmrc, and is probably worth noting somehow. Did I understand you correctly?

[brianreavis]

Yeah, --userconfig is just NPM's flag for explicitly setting a specific path to a npmrc file. I've been using it because I don't store it in a home directory. And right: pnpm install --config custom_npmrc should work the same way :) Haven't tested it... but yea! Should work. Was just wondering if this manager aims to be sort of 1:1, or if it's just best to note that --config is the way to do it with pnpm and move on.

The alternative is we open a PR on rc to support some some way of reading process.argv['user-config'] vs process.argv.config

[rstacruz]

Was just wondering if this manager aims to be sort of 1:1

Not really, but maybe 95% there. With the store model pnpm is doing, there are likely some things that we can't do.

I'm happy with not supporting --userconfig when --config does just fine — there are more important npm flags to implement, really.

One way we can do that is simply to pass process.argv with --userconfig swapped out for --config (rc('npm', {}, argv))

[rstacruz]

closing this for now... it seems it's not really that important.

if anyone disagrees and needs this option, just voice it out and let's consider it again by then.

[zkochan]

I suggest to support the npm parameter to avoid confusion.

[danielbayley]

As mentioned in #695, pnpm should also respect $NPM_CONFIG_USERCONFIG as npm does.