I believe most npm packages do not include tsconfigs in their output.
But even if they do, they don't include the ts[x]? files, so the tsconfig will match no files.

It'd be interesting to see how many npm packages you have installed actually have them. You can do this via the following snippet:

const {sync} = require('glob');
console.log(sync("./**/tsconfig.json"));

What does your project structure look like?
Do you follow the "standard" monorepo structure (i.e. the same structure we have in this repo)?
Or do you have another structure?

See issue on OOMs: #1192

OOMs happen because typescript isn't overly optimised for our usecase, nor is our codebase overly optimised yet.
As more projects get added, each one adds memory usage. We haven't figured out a strategy for purging projects from memory yet, so memory usage currently just grows.

As mentioned, NPM packages should have a tsconfig that matches zero files, so their impact on memory should be negligible. Your projects would be 99%+++ of the memory usage.

See https://github.com/tkalliom/monorepo-typescript-linting-example/ for an example of a project where the wider glob catches enough node modules for the memory to run out

Your example doesn't cause memory to run out for me, but it does show that I'm wrong, and there are many package maintainers that are lazy, and do not exclude the source files from their packages.

> const {sync} = require('glob');
undefined
> console.log(sync("./**/tsconfig.json"));
[
  './ecommerce/operation-a/tsconfig.json',
  './ecommerce/operation-b/tsconfig.json',
  './ecommerce/operation-c/tsconfig.json',
  './ecommerce/operation-d/tsconfig.json',
  './fulfillment/operation-a/tsconfig.json',
  './layers/ecommerce-shared/tsconfig.json',
  './node_modules/@bcoe/v8-coverage/dist/lib/tsconfig.json',
  './node_modules/@bcoe/v8-coverage/tsconfig.json',
  './node_modules/commandpost/tsconfig.json',
  './node_modules/dtsgenerator/example/add-prefix/tsconfig.json',
  './node_modules/dtsgenerator/example/tsconfig.json',
  './node_modules/dtsgenerator/tsconfig.json',
  './node_modules/rxjs/src/tsconfig.json',
  './node_modules/schemats/node_modules/typescript-formatter/example/tsconfig.json',
  './node_modules/schemats/node_modules/typescript-formatter/tsconfig.json',
  './node_modules/schemats/tsconfig.json',
  './node_modules/uri-js/tsconfig.json',
  './purchase/operation-a/tsconfig.json'
]

A few of those contain non-trivial ts sourcecode in their package, like dtsgenerator and rxjs.

In that case, I think that it makes sense to add a new option to ignore certain folders from the glob, defaulting to ['/node_modules/'].