Handling Effect Version Compatibility in a Library
I'm working on a library for writing Next.js Server Actions, Forms & route handlers with Effect (https://github.com/useflytrap/next-effect), but the problem is that as soon as the user of my package is on a different version of Effect, they will get type errors.
Now I know from other discussions that Effect does this for a reason, but I want to understand as a library author, what we can do to solve this problem for our users? Because having an "Installation step" for "Add Effect version X to
Now I know from other discussions that Effect does this for a reason, but I want to understand as a library author, what we can do to solve this problem for our users? Because having an "Installation step" for "Add Effect version X to
"resolutions"
Production-grade applications in TypeScript.
6,221Members
Resources
Recent Announcements
Similar Threads
Was this page helpful?
