Multi file support

[Gozala]

Feature request

This is more of feature request than an actual issue. Often times during development I use Quokka.js to test things out, which works great one things are scoped to a single file (module). Unfortunately more often than not things are broken up across multiple files and being able to trace what is going on in that other file would be extremely helpful in figuring things out.

Note that while I can start quokka on those files I won't be able to trace calls from one to the other.

I'm running quokka on vscode but I suspect this would be the same across other editors as well.

[ArtemGovorov]

Quokka doesn't support multi files, but our other tool called Wallaby (test runner), does support it.

[simonl65]

Ah! I didn't spot this before purchase 👎 Given that almost all development these days makes use of modules, are there any plans to enable multi-file/modular javascript support?

BTW: With vscode I see the [--=----] (spinner?) and Quokka appears unresponsive - is that due to this issue?

[ArtemGovorov]

@simonl65

Given that almost all development these days makes use of modules, are there any plans to enable multi-file/modular javascript support?

Just to clarify a bit - Quokka supports loading/running multiple modules, it's just showing inline messages/coverage in an entry one (the one you start Quokka on).

With vscode I see the [--=----] (spinner?) and Quokka appears unresponsive - is that due to this issue?

This shouldn't be related to modules. It may be related to the fact that your node program never stops (so Quokka keeps running). Please create a separate issue and share some code where we can reproduce the issue.

[simonl65]

@ArtemGovorov I undertand - thanks for the clarification.

Regarding the spinner - I've opened new issue #202

[bugs181]

I'd like to give my input. I think this feature request should be reconsidered. There are times where I don't need the full TDD/BDD suite and just want to see what's going on in multiple files. I had planned to purchase both tools after several days of trial, however probably won't until this feature is implemented. As it stands, Quokka is great for "toy experimentation" to see how something behaves but fails at providing good information in existing projects.

[ArtemKolichenkov]

I think this must be more prioritized. When I bought Quokka it was fun to play with for simple things, but unfortunately without multifile support using Quokka often results in wasting more time than just doing console.logs (meaning you have to move everything into one file if you want to see the full picture, nobody has time for that).

IMO Providing at least 3-4 files tracking depth(imports) is crucial for anything more complicated than basic learning tasks. Can be quite tricky to implement efficiently, but that would make Quokka much easier to be recommend than now.

[bugs181]

Bump.

[rvhelden]

I'm really missing this feature, like using speed profiling or other live comments in imported project files

[rdhar]

A year from the last comment, and two years since opening: is there any plans to implement this in the roadmap?

[smcenlly]

Not at this point in time. There's actually significant technical complexity in doing this. Our other product, Wallaby.js allows you to do this in the context of running your tests. We're are also working on another product idea that will allow you to do a similar thing from front-end frameworks (when using your browser). If you have not already subscribed to our mailing list, it's a great way to keep up to date with our news.

[rdhar]

Thanks, @smcenlly, appreciate your response. Looking forward to hearing more about this new product concept.

At this point, I'm not inclined to subscribe to the mailing list since the vast majority of items is with regards to Wallaby, rather than Quokka. Perhaps, having a regularly-updated changelog for each product would go some way towards transparency of the updates for both tooling.

I know I would find it more encouraging to renew my license if I was aware of what new updates I'm missing out on.