title: Why would new Date return invalid in the mongo shell when it returns a valid date in Node REPL?
body: <p>In Mongo (technically RoboMongo): </p>
  
  <pre><code>db.audit.find({source: "junebug"}).limit(50).forEach(function (doc){
  
    print(JSON.stringify(doc)); 
    print(doc.start);
    doc.startDt = new Date(doc.start + 'Z');
  
    print(doc.startDt);
  });
  </code></pre>
  
  <p>produces things like: </p>
  
  <pre><code>{"_id":{},"source":"junebug","maxDays":0.05,"start":"2016-11-03 00:00:00","end":"2016-11-03 00:59:59" ...
  2016-11-03 00:00:00
  Invalid Date
  </code></pre>
  
  <p>So, <code>"2016-11-03 00:00:00"+"Z"</code> is invalid. But in the Node REPL: </p>
  
  <pre><code>&gt; var d = new Date("2016-11-03 04:00:00"+"Z")
  undefined
  &gt; d
  2016-11-03T04:00:00.000Z
  </code></pre>
  
  <p>Looks valid. Is valid. I'm at a loss to explain why this would be happening. I can't imagine there would be a difference in date parsing between Node 6 and Mongo's js engine. </p>