[Feature]: Javascript target

[Sgregory42]

Problem statement

I cannot use dream_test in a javascript project (frontend)

Proposed solution

To dream_test to support javascript target (or maybe somehow isolate the dream runner ?)

Proposed API (if applicable)

Alternatives considered

No response

Fits dream_test's philosophy?

NA

Would this be a breaking change?

No, fully backward compatible

Current workaround

No response

Additional context

No response

[dcrockwell]

We haven't had any need for javascript as a target, yet. As such, we don't have a project to understand what would be needed. There are some features that inherently seem like they wouldn't work, for example test file automatic discovery.

If you could give us an idea of which features are not working with a javascript target, maybe we could find a way to enhance the framework for it. Otherwise, I think it would require pairing with someone that has a javascript project (which I'm willing to do for a few hours each week), or a community PR.

Are you open to pairing a bit over discord/google meet to understand how your project works, so we can learn the scope of the changes needed?

[Sgregory42]

Hum, I am not sure for now. I am still experimenting I think if I isolate the domain logic and lustre (without any ffi) I can run it in erlang. Not 100% ideal as I would want the tested code to be the same as prod.
(as in -> have the logical part in a shared library, run the test in erlang target, but when I will run the frontend it will be in javascript)

I am not yet sure of what should be the direction for now, I'll come back to this soon. I want to experiment a bit with lustre test helpers (simulate / query)