Use console.log instead of console.error

Finding linked packages is an expected outcome and
should not be considered an error. Logging with console.log
instead of console.error therefor seems more appropriate.

cmd.js

@@ -20,7 +20,7 @@ function cb (pkgName, foundPath) {
 function log () {
   var header = 'Some npm-link\'ed packaged were found:'
 
-  console.error(header + '\n' + list.join('\n') + '\n')
+  console.log(header + '\n' + list.join('\n') + '\n')
   process.exitCode = 1
 }
 

test/test.js

@@ -50,10 +50,10 @@ describe('simple project', function () {
     })
   })
 
-  it('should make cmd.js log an error', function (done) {
+  it('should make cmd.js log', function (done) {
     exec(CMD + pathToProject, function (err, stdout, stderr) {
       if (err) assert.ok(err)
-      assert.ok(/Some npm-link'ed packaged were found:/.test(stderr))
+      assert.ok(/Some npm-link'ed packaged were found:/.test(stdout))
 
       done()
     })
@@ -107,11 +107,11 @@ describe('nested project', function () {
     setTimeout(done, DELAY)
   })
 
-  it('should make cmd.js throw an error', function (done) {
+  it('should make cmd.js log', function (done) {
     exec(CMD + pathToProject, function (err, stdout, stderr) {
       if (err) assert.ok(err)
 
-      assert.ok(/Some npm-link'ed packaged were found:/.test(stderr))
+      assert.ok(/Some npm-link'ed packaged were found:/.test(stdout))
 
       done()
     })