Mathias Schäfer

Results 10 comments of Mathias Schäfer

Probably related question, is this duplicate `component` definition on purpose? TypeScript (4.6) complains about it. https://github.com/testing-library/svelte-testing-library/blob/main/types/index.d.ts#L26-L27 ```typescript component: SvelteComponent component: SvelteComponentTyped ``` ![Screenshot 2022-06-02 at 14 28 00](https://user-images.githubusercontent.com/51251/171629347-21ffc736-b474-4473-8260-2b03b2b0f52e.png)

@jdalton: Good to see the comments were added, they weren’t present when I had looked into the source some weeks ago. That’s the right direction.

That’s great news, thanks, @aFarkas

Is there any way to use `threads: true` while mocking or disabling jsdom? Disabling threads means losing many of vitest's benefits. Apparently, npm 7+ always installs `canvas` since it's a...

Hi, is there a potential fix or workaround for this issue? The minimal test case above still produces an error with the latest Jest and node-fetch. Thanks.

`` triggers this problem as well: ```html const numbers = [1, 2, 3, 4]; {#each numbers as number} {@const tag = number === 1 ? 'h1' : 'p'} {number} {/each}...

Cool, thanks for letting me know! This piece of code from 2010 was initially meant as an example what can be achieved with the selection APIs. Great to see that...

Great question! It's definitely in the scope of the book, but there are reasons why testing harnesses are not covered yet. When I wrote the better part of the book,...

I think I ran into the same issue with `` + `` (no JS). This is my minimal reproducible example: https://github.com/molily/vite-style-order index.html ```html body { color: blue; } ``` another.html...

Hi, first of all, thanks a lot for your efforts for this feature. I imagine that implementing it properly requires much consideration. I appreciate your goal to limit the scope...