The expect-more-jest package is still using a unstable 0.x.y release scheme (expect-more@0.8.1).

Shouldn't we wait until expect-more-jest has a stable release before using it?
Or are you OK with devDependencies potentially breaking?

EDIT: Turns out I got the versions mixed up, read my post below for accurate information.

Good point. Let's mark this as blocked

Whoops, I'm getting my versions mixed up...

I was looking at the expect-more package, and that's unstable at 0.8.1.
But expect-more-jest is stable at 5.2.1.

I did some more digging, and found that the expect-more-jest package does depend on the expect-more package:
https://github.com/JamieMason/expect-more/blob/master/packages/expect-more-jest/package.json

If we install expect-more-jest right now, we're also getting a unstable version of expect-more with it.
I'll leave you to decide how you want to weigh this, now that the information is actually accurate... 😄

In theory expect-more-jest should provide a stable API to us, and if the author changes anything underneath it then they will make it transparent to us. I think this tips it in favor of using it.

Hey @rarkins @HonkingGoose I just stumbled on this issue, despite the 0.x version I consider expect-more to be stable - it's on 0.x just because I haven't committed a breaking change yet, which would move it to 1.x. I could declare it 1.x to reflect that sentiment, but this is some background incase it's helpful.

Thanks

@JamieMagee I think semantic versioning is intended that pre-1.0.0 versions are liable to change API at any time (without bumping to 1.0.0) and that anything intended for production should be 1.0.0 or higher. When a dependency is 0.x it means users need to pay close attention to every update just in case it's changed API, as the maintainer is perfectly allowed to do. In short, anything ready for production should be 1.0.0 or later and anyone running things in production should try to avoid pre-1.0.0 packages (easier said than done..)

Anyway it looks like we can move ahead with expect-more regardless, thanks for clarifying.

Great, I'll bump it to 1.x when I next work on it too

(FYI 1.x bump is done)