Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

@matechs/node extensions wishlist

See original GitHub issue

There’s been talk about a NodeJS library for @matechs. Using this issue to document some feature ideas:

Ideas

File streams; reading and writing streams like in ZIO streams. ZStream.fromFile https://youtu.be/OiuKbpMOKsc 18:50
S.fromObjectReadStream mentioned in Slack.

Issue Analytics

State:
Created 3 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

1reaction

qlonikcommented, Jun 19, 2020

It would be nice to see fs methods wrapped into effects

0reactions

patrozacommented, Apr 28, 2021

Sorry, I misunderstood that we were talking about stream based fs methods only. For things like move/copy/delete/writeFile/readFile I’m not sure that stream based api is needed. I was thinking that even providing sync/async effect wrappers would be nice. Since effectify doesn’t handle overloads very well, and often manual wrappers need to be written.

But about stream based fs wrappers, I agree that in some cases it would be convenient to have stream based api. For example there is a handful of functions which either return or accept Node Streams, so those could probably be a good candidate to try how can we implement the support. Things like createReadStream and createWriteStream. There are also methods which return Buffer, which could potentially be a stream of buffer chunks (I dont know zio, but it seems like this is similar to their fs streams? Correct me if I’m wrong here).

What do you think @patroza ?

I’m totally for Effect and maybe even Sync wrappers. I keep repeating them over and over in my projects. Maybe good we start somewhere and extend as we find more usages?