Ev Haus

For me this is the one feature preventing me from migrating from `husky+lint-staged` to `lefthook`. I would love to see official/formal support for `git add` added as part of the...

Actually this is happening on Mac as well. I have to manually run `forever stopall` after Ctrl+C to ensure the server is killed. Changing title.

Thanks @htunnicliff. Works great!

I did notice one strange thing with `2.1.0-beta.0` though, the eslint [import/no-unresolved](https://github.com/import-js/eslint-plugin-import/blob/v2.26.0/docs/rules/no-unresolved.md) rule fails on: ``` import {use} from 'next-api-middleware'; ``` with this error: ``` 9:19 error Unable to resolve...

This issue is blocking the installation of both [Fork](https://fork.dev/) and [SourceTree](https://www.sourcetreeapp.com/).

We're seeing a similar issue. Upgrading Jest 25 made our tests slower when using coverage (166s with Jest 24 vs. 381s with Jest 25). With Jest 25 displaying many of...

> Any JS traces at all? This was printed: ``` ==== JS stack trace ========================================= 0: ExitFrame [pc: 0x521cca5be3d] Security context: 0x0ebfa799e6e9 1: _clearMemoizedQueries [0xebf2a5aba99] [/Users/evhaus/Git/zenhub/client/node_modules/jest-environment-jsdom/node_modules/jsdom/lib/jsdom/living/nodes/Node-impl.js:~208] [pc=0x521cd0d9a4e](this=0x0ebf5bee2aa9 ) 2: _clearMemoizedQueries...

@SimenB Rolling back just `jest-environment-jsdom` to `

For the following tests I don't have coverage enabled. - With `[email protected]` - 143s to run tests - No issues - With `[email protected]` - 154s to run tests - No...

> From all the comments here, it definitely sounds like coverage is the problem, and probably a regression in istanbul? I wouldn't be so fast to point the finger at...