Andrea Richiardi

So I added support for `sly` in [eval-in-repl](https://github.com/kaz-yos/eval-in-repl/blob/master/eval-in-repl-sly.el). However I am still not 100% satisfied with the flow.

Debugging purposes, understanding why things are failing and be less opaque. It would be opt-in so no change in current behavior.

The `npm publish` command was hanging and was not able to understand what was going on because the Observable was still `await`ing for things to finish. Thanks to the `--verbose`...

I am sure that it helped, because I basically did change the streaming target of the child observables and saw what was going on 😀

I respectfully think your arguments should be more specific and not just distrust what the other party is trying to explain. I will explain you way it was failing: the...

Ok thanks! No need to apologize :) I reported it just for other users' knowledge.

My 2c and thoughts. I am still unsure this should go in here as while devcards is very good to have in your workflow, many maybe are not using it....

About the last point, I guess it is particularly true if we ever want to use it as reactive library for backend stuff.

Chiming in here cause we ran into this. I wish I had found the @nivekuil's issue yesterday :smile_cat: There can be very weird interactions with tooling that add metadata to...

@refset Sorry I forgot to change that part, I was using `ofSeconds` 1 for my dev testing - yes indefinitely and no only one node.