Miguel Camba

@esbanarango sorry for forgetting about this. can you rebase?

@chriskrycho This kind of works, but apparently we should compile to JS + d.ts before publish. Any idea how we do that?

Probably no. I'd start over, and maybe, just maybe, use it for inspiration. Besides, chances are your typescript annotation will be more idiomatic.

In case we implement this I think I'd rather have `findByText`/`findAllByText` for parallelism with `find`/`findAll`. `match` makes me think in regular expressions, but perhaps it's just me. The most important...

@RuslanZavacky This library is only intended to be used in tests. Actually I believe you cannot even `import` any of this functions from outside tests.

Actually having a single helper that simulates a full key interation (fires keydown, keyup and keypress in sequence) sounds reasonable, the same way `click` fires mousedown, focus, mouseup and click...

I created the `under consideration` label and added to this issue. To see what other think. I'm personally :+1:, but I don't feel strongly either way.

Green light then for someone to implement it.

@rwjblue I can see how to modify the initializers to remove stuff between two known nodes, but any idea how to change the rendering to add those boundary markers?

@rgossiaux @akolyte01 I am one of the developers of https://github.com/DockYard/svelte-inline-compile. This week we plan to make it work for Vitest, a new trending test runner better suited for sveltekit apps...