isaacs/npm — pull request #1949 by welwood08 (2011-12-27 10:10:09+00:00)
Title: Treat a "No compatible version found" error as ENOTSUP

Currently, when an installation dependency can't be satisfied, npm directs users to submit the log here and treat it as an npm bug. This patch should make it more apparent that the problem is with the package being installed or its dependencies instead.

Example output of npm before patch:
```
npm ERR! Error: No compatible version found: sqlite3@'>=2.0.17- <2.1.0-'
npm ERR! Valid install targets:
npm ERR! ["2.0.0","2.0.1","2.0.2","2.0.3","2.0.4","2.0.5","2.0.6","2.0.7","2.0.8","2.0.9","2.0.10","2.0.11","2.0.12","2.0.13","2.0.14","2.0.15","2.1.0","2.1.1"]
npm ERR! at installTargetsError (/home/user/.nave/installed/0.6.5/lib/node_modules/npm/lib/cache.js:429:10)
npm ERR! at /home/user/.nave/installed/0.6.5/lib/node_modules/npm/lib/cache.js:411:17
npm ERR! at Object.saved [as oncomplete] (/home/user/.nave/installed/0.6.5/lib/node_modules/npm/lib/utils/npm-registry-client/get.js:136:7)
npm ERR! Report this *entire* log at:
npm ERR!
npm ERR! or email it to:
npm ERR!
```

Example output of npm after patch:
```
npm ERR! No compatible version found: sqlite3@'>=2.0.17- <2.1.0-'
npm ERR! Valid install targets:
npm ERR! ["2.0.0","2.0.1","2.0.2","2.0.3","2.0.4","2.0.5","2.0.6","2.0.7","2.0.8","2.0.9","2.0.10","2.0.11","2.0.12","2.0.13","2.0.14","2.0.15","2.1.0","2.1.1"]
npm ERR! Not compatible with your version of node/npm: sqlite3@'>=2.0.17- <2.1.0-'
npm ERR! Required: {"2.0.17":{"node":">=0.2.4 <0.5"},"2.0.18":{"node":">=0.2.4 <0.5"}}
npm ERR! Actual: {"npm":"1.1.0-alpha-6","node":"0.6.5"}
```

Related issues:
* #1309
* #1527
* #1589
* #1617
* #1669
* #1680
* #1684
* #1687
* #1690
* #1692
* #1747
* >> this patch created
* #1762 - unmet npm requirement
* #1791
* #1804
* #1810
* #1831
* #1836
* #1878
* #1885
* #1948