Avi Vahl

Any update on this one? This is the main thing stopping me from migrating to that test runner. :) My [previous comment](https://github.com/DefinitelyTyped/DefinitelyTyped/pull/62274#issuecomment-1250104125) about the context types can be addressed by...

Yeah, happens for the latest `sinon` version as well. `npm i` outputs: ``` > [email protected] postinstall C:\projects\postinstall\node_modules\sinon > node scripts/support-sinon.js Have some ❤️ for Sinon? You can support the project...

This issue came up as a possible blocker to move to project references several times on my team. We really want to use project references, but the current behavior of...

As a first step, we could add: `watchCompilerHost.useSourceOfProjectReferenceRedirect = () => true;` to `createWatchProgram.ts` (src of `@typescript-eslint/typescript-estree/dist/create-program/createWatchProgram.js`) Right before the call to: `const watch = ts.createWatchProgram(watchCompilerHost);` This will give **memory-wasteful**...

When I tested `useSourceOfProjectReferenceRedirect` locally, on two different mono-repos with project references, it worked without building even when I executed `eslint` from the command line. That was awesome. That flag...

Tested 4.4.2-alpha.1 in https://github.com/AviVahl/ts-tools Added the `EXPERIMENTAL_useSourceOfProjectReferenceRedirect` flag, and everything started working without me having to build. Running `eslint` just worked, and editing in the IDE stopped showing errors. :+1:...

@bradzacher this flag is going to make my coding experience so much nicer. thank you so much. Regarding the root `tsconfig.json` issue, I've checked the typescript api and behavior, and...

Here's a generator to make life easier: ```js /** * @param {readonly (ts.ResolvedProjectReference | undefined)[] | undefined} references * @param {Set} visited * @returns {Generator} */ function* filterReferences(references, visited =...

This is a small feature that can go a long way in terms of usability. I have a repo with several packages, where I'm using yarn workspaces for proper cross-package...

Noticed this today as well. The following `package.json`: ```json { "name": "test", "version": "1.0.0", "private": true, "dependencies": { "@types/create-react-class": "^15.6.0", "@types/react": "15", "@types/react-dom": "15" } } ``` Is resolved to...