Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork2.8k
Description
What code were you trying to parse?
// Put your code here
What did you expect to happen?
What actually happened?
Versions
package | version |
---|---|
@typescript-eslint/typescript-estree | X.Y.Z |
TypeScript | X.Y.Z |
node | X.Y.Z |
npm | X.Y.Z |
have chatted with@uniqueiniquity offline about this but once the files from the program are done, it is ok to close the watch so we can release program and its resources.. The common scenario is to have files in one tsconfig to be in a folder so likely to be iterated over together so it is possible to remoe the programA when files from programB are being queried and all the files (except say external files and lib files) are already iterated over.. Just need to keep track of files iterated.. The worst thing that can happen is to recreate program. (we would also keep flag if the program is recreated so that it is not purged after that so editing scenario keeps programs for the files being edited if that's how eslint works in editor scenario.. Needs some experimenting)
But this is the way we can work around the OOMs when there are multiple tsconfigs to be linted..
This is what will help issue reported atmicrosoft/TypeScript#35676 as just sharing source file wont be enough as that fix would delay OOM from say 5 projects to 6/7 but still not solve the main problem of having to create so many programs and create types