In monorepo (pnpm workspace), imported package loads no tsconfig.json

[Menci]

Acknowledgements

• I read the documentation and searched existing issues to avoid duplicates
• I understand this is a bug tracker and anything other than a proven bug will be closed
• I understand this is a free project and relies on community contributions
• I read and understood the Contribution guide

Minimal reproduction URL

https://stackblitz.com/edit/node-9cu3uzs2?file=packages%2Fa%2Fsrc%2Findex.tsx

Problem & expected behavior (under 200 words)

In packages/a run pnpm dev.

Expected behavior: prints two { type: "div", ... } objects.
Actual behavior: prints one and then throws "React is not defined" in imported package.

I guess tsx isn't using any of the tsconfig.json files and using the default config for TypsScript when transforming.

Bugs are expected to be fixed by those affected by it

• I'm interested in working on this issue

Compensating engineering work will speed up resolution and support the project

• I'm willing to offer $10 for financial support

[bradchristensen]

Edit: This seems to be fundamentally a duplicate of #96 (and #559 and #76), as it's the same underlying issue (tsx doesn't load tsconfig files in imported packages).

FYI there is a tiny problem with your repro - the main field of each package.json should be src/index.tsx (not .ts). Here's a fixed version: https://stackblitz.com/edit/node-x172jptg

---

I ran into this issue today too - in our monorepo, we use conditional exports, which would typically look something like:

"exports": {
  "types": "./dist/index.d.ts",
  "development": "./index.ts",
  "default": "./dist/index.js"
}

In production, the pre-compiled .js files are referenced (via the default conditional export), so tsc must be run to build dependencies first.

When we're developing things locally, we run tsx --conditions=development ... which means the .ts files get imported, and everything just magically works without the need to manually run tsc to build dependencies.

Previously we never had any React components in the shared packages, so we never noticed that they didn't work with this pattern until we tried doing so today.

[michaelschufi]

Hi @bradchristensen
Is the second part of your comment a working solution, or just an explanation of how you expect it to work?

I'm running into a similar issue. But my exports are structured like this:

// packages/utils/package.json
  "exports": {
    ".": "./src/index.ts",
    "./*": "./src/*.ts",
    "./next/*": "./src/next/*.ts",
    "./zod/*": "./src/zod/*.ts",
    "./zod/zod-utilz/*": "./src/zod/zod-utilz/*.ts"
  },

and it does not work when running pnpm tsx script.ts inside packages/app/script.ts where the script has a tsconfig with moduleResolution: bundler (or nodenext) and the workspace package is referenced in the dependencies. The error looks similar to this:

The requested module 'utils/zod/common' does not provide an export named 'dateCoerce'

but utils/zod/common has no imports using a tsconfig alias, meaning it should work.

[bradchristensen]

The second part of my comment was mainly to illustrate that this type of cross-workspace import works as expected when the Typescript files are compiled first (using tsc -b, which builds dependencies of the current workspace automatically) and then imported as JavaScript files (the "default" package exports). However, when tsx is used instead and it references Typescript files in other workspaces, the tsconfig files in those workspaces are not resolved and that could result in errors occurring if specific config is needed that differs from the defaults, such as the React config described in the repro above.

I'm not sure that the issue you're running into is the same one as this one but I can't tell from what you've provided - could you provide a stackblitz/codepen repro?

[michaelschufi]

Thanks for the reply. Yeah, I had a similar issue where tsx behaved unexpected because "type": "module" was not set in the workspace package dependency. This resulted in the same error and my initial thought was that I had to provide multiple export conditions instead of what I had there.

Sorry about the tangent.