Best Practices for Architecting Packages with Optional `effect` Types in JavaScript
Hello. Are there best practices for architecting a package which provides functions returning
I'm considering either exposing a runtime for consumers to do
effect types or JS built-ins? Consumers of my package may or may not be using effect in their projects.I'm considering either exposing a runtime for consumers to do
runtime.run*() or providing multiple entry-points where JS built-ins are pre-wrapped with a lazy executor—neither of which feel thrilling from a consumption standpoint.
