Have two different packages for Hspec and Tasty

Question

Would it be possible to have two different packages, one for Hspec and one for Tasty?

Currently, when one chooses to use Hspec (resp. Tasty), they also have to compile Tasty (resp. Hspec) as testcontainers-hs uses both as dependencies. But they won't actually use it.

Perhaps having something like this could help:

• The testcontainers-hs-core package would have all the definitions required to use testcontainers-hs, whether we're a Hspec user or Tasty user.
• The testcontainers-hs-hspec package for Hspec users
• The testcontainers-hs-tasty package for Tasty users

Do you think something like that would be doable?
Thanks in any case 🙂

Start by mapping the package dependencies and the Hspec and Tasty integration points in testcontainers-hs. Define the boundaries for testcontainers-hs-core, testcontainers-hs-hspec, and testcontainers-hs-tasty, then verify that users of either framework no longer compile the other dependency.