log time

Expected behaviour

0|server   | 2017-03-25 18:29:46.4920: Using files from public directory.
0|server   | 2017-03-25 18:29:46.5040: Server successfully launched at http://localhost:3000?react_perf (development)
0|server   | 2017-03-25 18:29:46.5040: To profile components open Chrome DevTools Timeline tab. Events grouped under User Timing.
0|server   | 2017-03-25 18:29:46.5040: To stop development server use yarn pm2:stop
0|server   | 2017-03-25 18:29:46.5040: ———————————————————————————————————————————————————————————————————————————
0|server   | 2017-03-25 18:29:49.6250: webpack built 49b71f7f794f7dcf59f8 in 3146ms

Actual behaviour

0|server   | 2017-03-25 18:29:46.4920: Using files from public directory.
0|server   | 2017-03-25 18:29:46.5040: Server successfully launched at http://localhost:3000?react_perf (development)
0|server   | 2017-03-25 18:29:46.5040: To profile components open Chrome DevTools Timeline tab. Events grouped under User Timing.
0|server   | To stop development server use yarn pm2:stop
0|server   | 2017-03-25 18:29:46.5040: ———————————————————————————————————————————————————————————————————————————
0|server   | 2017-03-25 18:29:49.6250: webpack built 49b71f7f794f7dcf59f8 in 3146ms

Problem

As you can see I don't get time for To stop development server use yarn pm2:stop and this happens randomly...

Software versions used

OS         : Linux Ubuntu 16.04
node.js    : 7.7.4
PM2        : 2.4.2

Start by reproducing the intermittent missing timestamp in the server startup output on the listed Ubuntu, Node.js, and PM2 versions. Trace the logging path that emits “To stop development server use yarn pm2:stop”; done means that line consistently includes the same timestamp format as the surrounding messages.