@DanielRosenwasser The relative reference resolutions are also dependent on rootDirs option in config file. I am wondering if we should create inferred configured project that only reads options from config file and not file list so we give more accurate result.. Thoughts?

@typescript-bot pack this

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

I'm not quite as concerned with rootDirs, but maybe that's a bias of not having seen it nearly as much. If we're willing to read the tsconfig.json, then we probably also want to respect path mappings from the paths field too.

By the way, what's the difference between this and #39476?

Oh, is the idea that you would load up the entire project except for non-relative modules (e.g. node_modules imports)? From a gut feel, I don't think that that's desirable. I think a lot of codebases are large enough from their own size and we really want to minimize program construction time.

Thats correct.. It constructs relative reference tree and ignores node_module imports.
The other one just resolves only in open file (only relative references)

@typescript-bot pack this

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

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/79104/artifacts?artifactName=tgz&fileId=11930698DC3312C59AF49D30296B7784B5F0BAA312D949B81C2C9A5C62932C9702&fileName=/typescript-4.0.0-insiders.20200707.tgz"
    }
}

and then running npm install.

Hey @sheetalkamat, something went wrong when looking for the build artifact. (You can check the log here).

Closing this since we definitely dont want whole tree.