TypeScript Monorepo support?

[AlCalzone]

I apologize in advance if this has been asked before, but I didn't find anything. I am maintaining a TypeScript monorepo managed with lerna and yarn workspaces, where I write some maintenance scripts in TypeScript.

To run these, I currently use ts-node, but that requires the referenced projects to be compiled first. Seems to be the same with esbuild and the esbuild-runner, but I guess there is a way that this should not be necessary.

Am I missing something or is this just not possible yet?

[evanw]

I'm not familiar with the Lerna and Yarn ecosystems. You'll have to be specific about what isn't working with esbuild. Can you provide a code sample?

[AlCalzone]

I'll see if I can create a repro repo tomorrow. This is not easily explained.

[hardfist]

I did use esbuild in monorepo，and i donnot need to compile reference package first，all i need todo is to add an source field to package mainfield which points to source file，then configure esbuild bundle mainfieldoptions which resolve source field first

[AlCalzone]

Got a link where I can see that?

[AlCalzone]

While playing around with my repro repo, I got it to work when the root tsconfig.json contains paths for each package.
In my original repo that didn't work, so there must be something else going on in my repo.

Feel free to close this, although mentioning the paths setup could be something for the docs.

[camsloanftc]

I am currently trying to solve this as well and noticing this seems to be a general ts monorepo problem more than an esbuild problem. I just wanted to share this other repo that I came across that is handling typescript monorepos with a number of different use cases. Maybe we can add an example there for using esbuild.

[evanw]

Are there situations where TypeScript works but esbuild doesn't? Is there something about tsconfig.json handling?

[lukeed]

I found this on Twitter this morning – uni
I havent tried it out or anything, but maybe you'll find it useful @AlCalzone

In my projects, I just have a node script that starts a service, and then I loop through my packages/ structure, looking for & responding to any configuration files.

[Ventajou]

been using esbuild in a TS monorepo (using Yarn Workspaces) for months now, I never had an issue.

And I'm not using any paths trickery in the root tsconfig, this is what it looks like:

{
	"compilerOptions": {
		"module": "esNext",
		"target": "es2017",
		"moduleResolution": "node",
		"sourceMap": false,
		"emitDecoratorMetadata": false,
		"experimentalDecorators": true,
		"esModuleInterop": true,
		"removeComments": true,
		"noImplicitAny": true,
		"declaration": true,
		"jsx": "react",
		"allowSyntheticDefaultImports": true,
		"importHelpers": false,
		"forceConsistentCasingInFileNames": true,
		"skipLibCheck": true,
		"skipDefaultLibCheck": true,
		"incremental": true,
		"importsNotUsedAsValues": "preserve",
		"composite": true,
		"declarationMap": true,
		"typeRoots": ["./node_modules/@types", "./types"]
	}
}

And here's what the tsconfig looks like for most packages:

{
	"extends": "../../../tsconfig.json",
	"compilerOptions": {
		"baseUrl": "./",
		"paths": {
			"~/*": ["src/*"]
		}
	}
}

[hardfist]

Got a link where I can see that?

https://github.com/hardfist/neo-tools/blob/main/packages/playground/scripts/build.ts#L19 && https://github.com/hardfist/neo-tools/blob/main/plugins/glob/package.json#L6

[AlCalzone]

@hardfist Thanks - however I'm using esbuild-runner which doesn't seem to have an option to pass this to esbuild.

[evanw]

I'm going to close this since it sounds like this something that is custom to specific project setups and is solved through configuration files. If this works with esbuild but not with esbuild-runner, then this sounds like an issue with esbuild-runner not with esbuild.