Exporting all types?

[rob-gordon]

I'm building some cool things around cva but one thing that makes it difficult is that only some of the types are exported from the library. Would there be any harm in exporting all of the internal types? Especially Class Value and Config.
That would make it easier to extend cva or use it in different ways but maintain type-safety. I'm happy to open a PR if the maintainers are alright with it 👍🏻

[joe-bell]

Sorry, I don’t think this is something I want to export unless it’s something I feel comfortable maintaining

Keeping it internal allows for more flexibility at the moment

Happy to reconsider later

[rob-gordon]

I understand not wanting to add to the maintenance cost.

For context, type access allowed me to build a helper function for creating components directly from cva (built an example on a fork with types). I could imagine other people might find it useful too if it were a possibility.

[joe-bell]

Nice! I intentionally chose not to include that kind of API, but glad to hear you’ve found something that works for you

I’ll let you know if I change my mind on exporting types! May reconsider for v1

[ksandinunikum]

I think this would be a great addition to CVA. I have also created typesafe extension utilities for CVA, and currently I have to redefine all the internal types. I think CVA is a really composable library fundamentally, but without also exposing the type definitions of its data structure, that composability will be limited to javascript only.