Ivan Rubinson

So the workaround is to use version `3.3.0`... which is 4 years old at this point.

Looks like the root cause may be an issue with the implementation of a fix done years ago: [track updating status to remove race condition that deletes watchers](https://github.com/browserify/watchify/commit/847c5490c15a53cec456491442e08e092535d04d) Commenting out...

The offending line of code is specifically `bundle.on('error', onend);`. If this is commented out, this bug stops happening. Perhaps we're preventing browserify from handling the error properly by overwriting the...

Consider using an HTML element with CSS style: `position: fixed; top: 0; left: 0; width: 100%` for a header `position: fixed; bottom: 0; left: 0; width: 100%` for a footer

This is especially a problem when `c/c/c.ts` has `import from '../../a'`, because then the import has an extra `../` making it import from the source rather than the outputs directory.

@coderhammer what did you change? Is there a workaround?

@coderhammer If you think the issue is with test configuration, where do you think the issue is? I thought it could be that `Test.createTestingModule` from `@nestjs/testing` is bugged, so I...

Also I don't think that `app.enableShutdownHooks` is related, because in the MCVE tests I linked if I comment out `enableShutdownHooks` it still fails with the same error. (clearly that means...

@coderhammer Looks like Supertest may be related, but is not the only issue. I added to the MCVE a suite that does the same tests but without Supertest. The same...

With the simplest possible Express application (without even Terminus) it acts the same as with Nest not using Supertest. ```javascript const express = require('express'); function createServer() { const app =...