npm: use npm_config_prefix instead of NPM_CONFIG_PREFIX

[vincentbernat]

Recent versions of npm (at least 1.4.21) don't accept
NPM_CONFIG_PREFIX being valid. They expect the lower-case version
instead. Since I don't know for sure that older versions also accept
that, I keep both of them.

[ekalinin]

Hi @vincentbernat, thanks for report & hotfix!
But can you provide more details about error?

I just checked and didn't get any errors:

➥ virtualenv env
➥ . env/bin/activate
(env) ➥ pip install nodeenv
(env) ➥ nodeenv --version
0.11.0
(env) ➥ nodeenv -p --prebuilt
(env) ➥ npm -v
1.4.23
(env) ➥ npm install -g sitemap
[email protected] ~/tmp/env/lib/node_modules/sitemap
(env) ➥ npm install typogr
[email protected] node_modules/typogr
├── [email protected]
├── [email protected]
├── [email protected] ([email protected])
└── [email protected] ([email protected], [email protected])

[vincentbernat]

❦ 20 août 2014 14:30 -0700, Eugene Kalinin [email protected] :

Hi @vincentbernat, thanks for report & hotfix!
But can you provide more details about error?

I just checked and didn't get any errors:

Maybe this has been fixed later?

When I do "npm -g prefix", I get /usr/local, but with "env
npm_config_prefix=/something npm -g prefix", I get /something. What do
you get? I don't have the bandwidth currently to use anything else than

"nodeenv -p -n system", so I end up with npm 1.4.21.

printk("Entering UltraSMPenguin Mode...\n");
2.2.16 /usr/src/linux/arch/sparc64/kernel/smp.c

[ekalinin]

Thanks for patch!