Upgrade date-fns@2

[bengry]

date-fns@2 has been released, and since listr-verbose-renderer is pinned on ^1.x.x, it makes it hard for users listr-verbose-renderer to use date-fns@2 simultaneously, due to conflicting packages.

This PR updates this dependency.

Note that this is a breaking change in listr-verbose-renderer for users who may have passed an invalid format (which previously worked) due to a breaking change in [email protected], to better conform the unicode standard

[bengry]

@SamVerschueren I'm not sure why the tests fail in Node 6. Can you please advise?

[SamVerschueren]

This is weird, according to the docs hook-std should be used differently 🤔 ...
https://github.com/sindresorhus/hook-std/tree/v1.1.0#usage

https://github.com/SamVerschueren/listr-verbose-renderer/blob/master/test/fixtures/utils.js

Looks like it should be something as this

'use strict';
const hookStd = require('hook-std');
const stripAnsi = require('strip-ansi');

exports.testOutput = (t, expected) => {
	t.plan(t._test.planCount || expected.length);
	let i = 0;

	const promise = hookStd(actual => {
		t.is(stripAnsi(actual), `${expected[i++]}`);

		if (i === expected.length) {
			promise.unhook();
		}
	});
};

[bengry]

@SamVerschueren what's the difference between what's currently in https://github.com/SamVerschueren/listr-verbose-renderer/blob/master/test/fixtures/utils.js and the snippet you posted in #8 (comment)?

They look the same to me.

Also, note that I didn't change the file in the first place. I'm not sure if master would even pass the above test with any minor changes to it (there's no lock file in the repo, which may be the cause of the discrepency)

[SamVerschueren]

The difference is the promise.unhook() instead of just unhook(). Not sure why that would only fail on Node.js 6 though...

[bengry]

@SamVerschueren I missed that in the diff. Thanks.
I pushed the change to this branch and seems like Travis is now happy in all checked versions.

Is this something that you want to merge to master and release a new version for? I mentioned the reasoning behind this PR in the OP.

[maraisr]

Mega keen on this merge!

[bengry]

@SamVerschueren any update on this?

[SamVerschueren]

Sorry for the late replies and lack of response from my side. Released as 0.6.0.

[SamVerschueren]

Thanks for working on this! 🎉