Closed Almaju closed 4 months ago
Hey, nice job! This is definitely worth sharing on the Effect discord and maybe even make this example part of the official @effect/platform
readme because I remember few people asked about the express <> /platform interop in the past already. And your impl seems to be independent of this lib so you cover wider audience than just users of effect-http
. So go ahead and start a thread in the Effect discord, I'm sure you'll get lot of people excited and you might get a valuable feedback from the community!
After the feedback, feel free to open a PR with a readme or example in here, but the official /platform package is maybe even better place. Also, I think it could deserve it's own package potentially. I think the size of this snippet will increase as you'll start tackling different edge cases / problems, again, I recommend to open this topic with the Effect community 🙂.
I am currently working on an Express based codebase and I am trying to switch to effect-http in a non-breaking way. I wrote a small adapter to wrap Express and be able to do that, I thought this could be of interest. Not sure this deserves its own package but it could be useful as an example somewhere?
This is what it looks like:
The implementation: