pro tip: npm config set save-prefix='~'

[Andrew Kelley]

that is all.

[mscdex]

https://www.npmjs.org/doc/misc/npm-config.html#save-prefix

[Luiz Filipe]

What is the meaning of this command?

2014-06-30 19:49 GMT-03:00 Andrew Kelley <super...@gmail.com>:

that is all.

--
Job board: http://jobs.nodejs.org/
New group rules: https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+un...@googlegroups.com.
To post to this group, send email to nod...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/afa22221-cea2-421d-8774-50f82feb6b12%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Best Regards,

Luiz Filipe
WebGL, node.js and JavaScript Developer

Fortaleza CE

[Alex Kocharin]

 

You forgot "npm set spin false", "npm set loglevel http", and... well... "npm install -g yapm; alias npm=yapm" would also help since npm now is... well... less than ideal (I hope npm 1.5 will fix most of that).

 

 

01.07.2014, 20:18, "Andrew Kelley" <super...@gmail.com>:

[Forrest Norvell]

> since npm now is... well... less than ideal

How so? Bugs? Features? The registry?

>  (I hope npm 1.5 will fix most of that).

I'm working hard on 1.5.0 right now and need help figuring out where to focus my attention. Issues filed and pull requests with tests are extremely helpful!

F

To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/5812791404288722%40web12g.yandex.ru.

[Andrew Kelley]

this is wonderful, thank you. Ahh so much better.

[Alex Kocharin]

 

I'm waiting for scoped packages support, which will hopefully fix two issues: namespaces in The Registry, and support for other registries.

 

Another big thing I'm waiting for is pre-building dependency tree before installing anything. I tried that, it can't be done easily in several lines of code (like semver support for github packages for example), so I didn't risk changing it locally or sending a pull request (those were rarely accepted a year ago, don't know how it is now).

 

Other than that... npm doesn't preserve package.json formatting. No comments support in there (please move to package.json5 format already, which can be converted to package.json on publish...). And last I checked, even comments in .npmrc gets removed after its update (even though with ini it's easy not to do). But those things were under "isaacs-says-no" label for years, so I don't really have any hope. On the other hand, so were namespaces, but here they are.

 

All issues I know about are old ones, so they are already filed multiple times by different people. Only one recent addition in "please change" list is the spinner, thankfully it's easy enough to disable.

 

 

// alex

 

03.07.2014, 01:58, "Forrest Norvell" <othi...@gmail.com>:

To view this discussion on the web visit https://groups.google.com/d/msgid/nodejs/CAHG3qKpabQ4eKWvFig9Ze_SE3c3hDLhdoWu5A13HuApZHdWPrg%40mail.gmail.com.