Replies: 2 comments
-
This also leads to issues where you can't use typeschema in a bundler without listing all of the externals just like the special vite integration that shouldnt be needed imo |
Beta Was this translation helpful? Give feedback.
0 replies
-
Solved as part of |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
hello @decs ,
tell me if i'm wrong, but i expect typeschema target audience to be library implementor like :
i don't expect application level to need this, because being tied to only one validation library is fine for an application.
if that's the case, i think it would be a good idea to let the library authors to pick what adapters they want to include by default.
because having a huge list of resolvers in the typescript registry can deeply impact typescript performances.
Allowing library author to cherry pick the minimum set of libs would allow to have correct performances if they support only 2 or 3 libraries by default, while still allowing their users to add the one they want if it's not in the library default list.
So i propose to split the library in a monorepo, with all adapters in their respective packages.
what do you think ?
Beta Was this translation helpful? Give feedback.
All reactions