You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is indeed problematic. Any project relying on ts-node, such as Nx, breaks in a pretty opaque way when working in a context where the tsconfig.json extends a config exposed through a dep's exports path, which is what we do at work for our centralized configs package.
Worried that this issue has been unacknowledged for 6+ months
Search Terms
exports, package.json, tsconfig, extends, base config
Description
While tsc works and resolves the config files from the exports fields of the packages, ts-node fails.
Expected Behavior
ts-node finds and reads extended configs from an external package when they're defined in the
packageJson.exports
field.Actual Behavior
ts-node fails to parse the config and exits with an error.
Minimal reproduction
Repro: TypeStrong/ts-node-repros#39
This setup includes two packages
@tsnode-exports/main
a regular package and a@tsnode-exports/ts-config
holding just the base tsconfig file.in package
ts-config
the tsconfig file is in some internal folder and is exposed via thepackage.json
field:exports
In package
main
we have a tsconfig with anextends
that points to that tsconfig in thets-config
package.Steps to reproduce the problem
v20.11.0
)npm ci
tsc
builds successfully by runningnpm run tsc
ts-node
fails to build by runningnpm run ts-node
Specifications
The text was updated successfully, but these errors were encountered: