@TavoNiievez currently we have a weird dependency situation:

1. module-asserts requires lib-asserts
2. module-asserts requires codeception
3. codeption requires lib-asserts
4. codeception requires module-asserts

I've chosen to simplify it by importing lib-asserts into module-asserts (seems a bit overkill to have those 2 repos separated).
My proposal is to deprecate lib-asserts and have this package provide it.

What do you think?

Edit: actually this is wrong; codeception only has a dev-require for this repo...

The real problem is modules depending on Codeception and vice versa.
Codeception/Codeception#6164 (comment)
In a perfect world, modules would be independent of Codeception, but in some cases this is difficult to achieve.

In a perfect world, modules would be independent of Codeception, but in some cases this is difficult to achieve.

Yeah, the whole module system is so complicated:

• Dependencies
• Conflicts
• Partial modules
• Dependent modules :-|

@SamMousa Do you still plan to integrate lib-asserts into this repo?

Honestly, the mess of circular dependencies made it so that a simple upgrade already took me a day without much results and I'm not inclined to spend more.