Schedule failed lookup updates

[sheetalkamat]

Schedule invalidation of module resolution cache on changes to failed lookup locations.
Fixes #37653

[sheetalkamat]

@typescript-bot pack this

[typescript-bot]

Heya @sheetalkamat, I've started to run the tarball bundle task on this PR at c80a83e. You can monitor the build here.

[sheetalkamat]

@weswigham does bot not pack build that fails to run tests

[weswigham]

Eeeyeah, it does not; it's templated off the publish task which, for sanity reasons, makes sure tests pass prior to publication. If you wanna override those sanity checks in a PR, you can always game the system a little bit and edit the Gulpfile to not actually test anything while you're getting trial builds made (eg, by deleting the contents of the runTestsParallel task). It's a pretty good reminder that it's still WIP.

[sheetalkamat]

@typescript-bot pack this

[typescript-bot]

Heya @sheetalkamat, I've started to run the tarball bundle task on this PR at bd2f7b7. You can monitor the build here.

[typescript-bot]

Hey @sheetalkamat, I've packed this into an installable tgz. You can install it for testing by referencing it in your package.json like so:

{
    "devDependencies": {
        "typescript": "https://typescript.visualstudio.com/cf7ac146-d525-443c-b23c-0d58337efebc/_apis/build/builds/73861/artifacts?artifactName=tgz&fileId=3E697F8F13F606B519C3FE6EA0DAFDE2E5BBE7A6B6C747B1B14789B23967C11C02&fileName=/typescript-4.0.0-insiders.20200514.tgz"
    }
}

and then running npm install.

---

There is also a playground for this build.

[andrewbranch]

These changes make sense to me; it’s clear where you’re throttling an operation that was previously not throttled. The only thing that I can’t figure out is why this wasn’t a problem with npm as well as yarn.

[sheetalkamat]

@andrewbranch i dont understand what you mean. #37055 changed how module resolutions are updated and that means that npm/yarn install notifications were producing lot more work to check if things need to be invalidated. Before that PR we would just mark project as ready for update and schedule one which would keep on cancelling and scheduling so not much work involved in there. This PR merges both behaviours by scheduling invalidation of module resolutions so we can process them all at once instead of on every notification from FS.

[andrewbranch]

Ok, I was under the impression that this bug was unique to yarn.