Justin Leider

I see that the tests have been updated: https://github.com/TypeStrong/ts-loader/pull/1003/files#diff-18ab58ce03516261da5fb32ec3f05984R108 and I dont get that error anymore but I also still get all the other definition files have not been built...

I pulled down the latest updates locally and ran the tests again. I am still getting the following test failures. Additionally, one thing I have noticed about the tests is...

I am using MacOS v10.14.6. I tested with both Node v11.15 and v12.8. TypeScript version v3.6.3 for my own project and whatever `ts-loader` requires for the tests. I sync'ed my...

Also, I suspected that `fork-ts-checker-webpack-plugin` could be causing issues in my own project so I removed that from my webpack config and tried with `transpileOnly: false` and get this TypeScript...

@sheetalkamat I have three things to report: 1. Between the 6.1.1 and 6.2.2 changes this is mostly working! However, there is still one issue that seems to be a race...

The repro for 1> is the existing test which fails: `yarn run comparison-tests --single-test projectReferencesNotBuilt` ``` yarn run comparison-tests --single-test projectReferencesNotBuilt 09/23 13:36:23 115.637s yarn run v1.17.3 $ git clean...

Looks like I hadn't rebuilt the src before running the tests. That test passes now. However, I don't have a repro for you at this moment since our code base...

@t83714 I believe this is actually an issue with tsconfigs not ts-loader as I have struggled with this a bunch recently. It would seem that there is no way to...

Looks like there has been some progress made regarding an api: https://github.com/microsoft/TypeScript/pull/31432

@milessabin Benchmarking our slowest project (91 files) the `-Yinduction-heuristics` flag with Scala 2.11.11-typelevel-4 shows a ~25s improvement on a 300s compile. Clearly there is something else at work here, perhaps...