Jake Bailey

> Didn't anyone else or any test suite notice the issue? It's a 3x slowdown here, not subtle. There is no test that can catch this sort of issue. (There...

That's all set up and should "just work" even in the non-submodules test with just a reference directive: ``` /// ``` The code we have for it isn't specific to...

Ohh, the test runner doesn't skip the test when the submodule isn't cloned; should be easy to fix.

Applying this patch should do it: ```diff diff --git a/internal/testutil/harnessutil/harnessutil.go b/internal/testutil/harnessutil/harnessutil.go index 3f4474789..9c02222fb 100644 --- a/internal/testutil/harnessutil/harnessutil.go +++ b/internal/testutil/harnessutil/harnessutil.go @@ -146,6 +146,10 @@ func CompileFilesEx( } } + if includeLibDir {...

This will conflict with #2159 so I'll wait for that as it's more critical.

This is pretty atypical. Auto imports will never suggest these paths, and for more real published packages, you'd want to avoid this because you'd end up with files that are...

Maybe it's more clear to say "`.d.ts` files describe actual importable modules on disk". It is not advised by the TS team to write `.d.ts` files for any other purpose....

The existence of `./types.d.ts` file implies you are allowed to write `import "./types.js"` (or the CJS equivalent), that is, a runtime import. This is guaranteed to crash if there is...

Drafting this for now, until we can improve the checker situation IMO

The new codebase uses an all-new method to handle JSDoc where we actually rewrite the AST during parse to inject type nodes where TS files would have them, so some...