Some environments have a configured depth=x - if that depth is 0, like on travis or any other possible machine, the test failed. This passes Infinity, which is the current default in npmconf
The test in 8b5e7b6 fails as it depends on a unconfigured npm which uses exact the same values as a vanilla npmconf instance. This fix also does not depends on the external dependency npmconf.
`npm ls` and `npm star` already do, just `npm install` was missed.
I broke it with my changes to the common helper in 057d9b7.
Bonus: - Fix test in `startstop.js`
This test should turn green if read-installed is fixed and should avoid regressions in the future. This tests the cli, as it turned out that the programatical version of npm has a bug where depth=0 is not working
Added a simple example of installing npm by itself via curl. This helps solve [an issue](Homebrew/homebrew#27479) with the node homebrew formula where users will want a simple way to install npm after installing node. Homebrew maintainers would rather see this curl example in the npm README rather than directly in the node formula. It also just helps in general to have an example when users find the npm README and want to use the shell script.
The usual need-to-chdir-to-tmp-before-rimraf thing. Cleaned it up a bit while I was there.
the tests were depending on a warm cache, as npm was calling to a server on 1331 but the mock-registry was serving packages from another port. now a temporary cache location is used to avoid that the tests don't fail as they are getting everything from the cache. the server which served the metadata was removed, the metadata is now served by the mock-registry itself, so npm can also install from there. furthermore the package metadata was separated in files.
The GNU shell returns a code and no signal if it gets a SIGSEGV signal, so we have to skip this. Hat tip to @tjfontaine
move other non-standalone tests to test-legacy, and run them all on 'test-all'
I keep getting myself into weird cases where I have an outdated copy of npm-registry-mock, and so tests fail, and I spend several minutes digging only to find that it's because I didn't update after the package.json dep changed. Add a test to alert to this situation, which will run BEFORE all the other tests start failing horribly.
- npm install --save|--save-dev takes npm.config['save-prefix'] into account when prefixing the version in the package.json - by default the version is prefixed with '^' - added tests for this feature - added documentation for this feature including one example - tests are passing without npmconf changes, but this commit goes alongside [e045042] in npmconf repo
Regression caused by always fetching the root doc
Don't throw away that delicious metadata.
Hitting CDN and fs caches is always way faster, even if it does mean downloading more bytes on a cache miss.