Tim
Hm technically this is a breaking change. Feel free to submit it to the https://github.com/effect-TS/effect-smol repo.
Try overriding fetch with `FetchHttpClent.Fetch`. I'm not familiar with next.js's monkey-patching of fetch, so if that doesn't work you will have to revert to Effect.tryPromise.
Next is probably doing some weird source code transformations. Sorry but I don't think this is something we will fix anytime soon, unless someone more knowledgeable about next wants to...
I think it is worthwhile, debugging interrupts is painful at the moment.
/rebase
> it is but not sure how this helps debugging interrupts, it tells you where the program stopped and not who stopped it I feel like we could capture a...
It seems that is what you did in the latest commit? We could have the origin span and the receiver span, and then maybe set the error `cause` to the...
One other option is a namespace: ```ts typeof someEffect.Types.Success ``` But I think I prefer .Success etc directly on the type.
Hmm we will have to change the variance in some scenarios to make this work: It also seems to break the Effect.Success assignability where void is expected.
We might be able to use the same trick as the Iterators to disconnect the type helpers from the type variance. Will have a play around tomorrow.