title: Catching errors with Q.deferred
body: <p>I have a nodeJS project where I wish to use asynchronous functions. Namely, I'm using the <a href="https://github.com/kriskowal/q" rel="nofollow">Q</a> library.</p>
  
  <p>I have a function called someFunction(), that I wish to return a promise. With the then -function, I can then check whether the promise was resolved or rejected like so:</p>
  
  <pre><code>    someFunction()
      .then(
        function(results) {
          console.log("Success!");
        },
        function (error) {
          console.log("An error occurred, and I would wish to log it for example");
        }
      );
  </code></pre>
  
  <p>What I intuitively expect with the function above is, that the error function would catch all possible errors. So if some exception is raised inside the someFunction, I can rest assured, that the error function will be run (the second function after 'then'). But it seems this is not the case.</p>
  
  <p>For example, let's say the someFunction would be defined as so:</p>
  
  <pre><code>function someFunction() {
    var deferred = Q.defer();
    throw new Error("Can't bar.");
  
    deferred.resolve("success");
  }
  </code></pre>
  
  <p>Now if I call the function someFunction() like done in the upper code block, it won't run the error function. Why is that? Isn't the partial point of the promise Q.deferred to catch errors? Why should I manually reject every error that happens? I know I could set the whole content of someFunction to try/catch clause, and then reject the deferred, but that feels so wrong! There must be a better way, and I know for sure some of you stackoverflowers know it!</p>
  
  <p>With this information, I began to think about where the deferred.reject and deferred.resolve is even meant to be used? Is it even meant to catch exceptions? Should I really just go through all the error cases manually, and call the deferred.reject on them? I'm interested to hear how this should be handled professionally.</p>