Stephen Sorensen

What problem is solved by adding nested groups? For me, the problem is isolating setup/teardown hooks to specific tests. I don't want to create a separate test file just to...

I've never really understood the use case for `t.context` (or using `this` inside mocha tests)... what does `t.context` give me that I can't accomplish with a simple variable?

> Another option would be to use `.after` to register an after handler without having to make test return a promise After giving this some thought, I think this is...

If I do that, the teardown function won't get called when the test fails. That would likely cause lots of other tests to fail and make it difficult to debug....

For those who just need a quick workaround, here's how I fixed it in my code: Custom useForceUpdate hook defined elsewhere: ```js const useForceUpdate = () => { const [,...

Darn. Since the React team doesn't have time to work on this it looks like my best options at this point are to either fork my process or spawn two...

I used to like this idea. Now, not so much. I just spent the last week debugging and patching IE8 issues that are caused by shimming addEventListener, and these are...

He's setting config.resolve.plugins, not config.plugins, so I don't think that's the problem. I'm also experiencing this issue, and I verified that I experience this even when I'm not modifying the...

I switched from Chrome Canary to Chrome stable and it started working for me. Not sure if this is the same issue or not, but if you're using canary you...

What do you think of limiting the scope to a single identifier inside curly braces (`{myProp}`) that is equivalent to `myProp={myProp}`? For example: ```jsx ; // same as ``` Which...