Kevin Barabash

I ended up getting side-tracked by something else and have put my TypeScript development on hold.

@Brianzchen thanks for checking. I thought it might be an issue with [flow-define-type](https://github.com/gajus/eslint-plugin-flowtype#eslint-plugin-flowtype-rules-define-flow-type) since it's supposed to suppress `no-undef` when reporting type identifiers. I have `"flowtype/define-flow-type": "warn",` and `parser: "@babel/eslint-parser",`...

I'm trying to use `happy-dom` with `@testing-library/user-event`, but ran into an issue with simulated `tab` key presses not focusing the next tabbable element. I thought I could work around it...

It looks like progress is on-going in that PR, but it's a pretty big change. I could put together a PR that just replaces URL.ts with node's built-in `"url"` module.

If anyone is interested in the picking this up, the PR was a good start. There were a couple of issues that still need to be resolved, namely: - getting...

This seems to be work for me. I added a new file from the solution explore named `foo/bar/baz.fs` and it recursively created the directories that were needed as well as...

Is the intent of this option to store a top-level summary or are people looking for it to include coverage numbers for each file?

Thanks for opening this ticket. 🙂 The analysis of what's mocked and isn't mocked doesn't have to be perfect. It would still be useful if it could handle simple cases...

FTR, I meant to say this **wasn't** the first time I forgot that I had mocked a module.

I would like to be able to do something like: ``` type AtLeastTwo = [T, T, ...T]; ``` This is for modelling an AST for a math expression parser that...