Best practices for peer dependencies in Effect-based SDKs
I'm creating an SDK that uses Effect and exposes Effect-based interfaces. Basically, users can write plugins that are dynamically loaded via
Should my package list effect and all of the various @effect packages that it uses internally (directly or indirectly) as peer dependencies?
tsx/esm/apiShould my package list effect and all of the various @effect packages that it uses internally (directly or indirectly) as peer dependencies?
Similar Threads
Was this page helpful?
