fix(misc): support ts-node options in tsconfig files

[forivall]

Current Behavior

The tsconfig.json is no longer being read by ts-node, and the ts-node specific options are also not being passed to ts-node.

Expected Behavior

The "ts-node" specific options should be read from the tsconfig.json files, ideally through the entire extends chain.

Related Issue(s)

Fixes #21695 - this PR doesnt read through the extends chain, but it solves my use case, where the options are in the tsconfig.base.json file. We can document that limitation, and I think it's a clear tradeoff.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Jun 4, 2024 7:24pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 88c6ee2. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 6 targets

• nx affected --targets=e2e,e2e-ci --base=9c2162fadcd976855326c0d2baa60673c2d9acc2 --head=88c6ee24ab5f582ae47b05150342e74b38b458d9 --parallel=1
• nx affected --targets=lint,test,build --base=9c2162fadcd976855326c0d2baa60673c2d9acc2 --head=88c6ee24ab5f582ae47b05150342e74b38b458d9 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=9c2162fadcd976855326c0d2baa60673c2d9acc2 --head=88c6ee24ab5f582ae47b05150342e74b38b458d9
• nx documentation --no-dte
• nx affected -t e2e-macos-ci --parallel=1 --base=9c2162fadcd976855326c0d2baa60673c2d9acc2 --head=88c6ee24ab5f582ae47b05150342e74b38b458d9

---

Sent with 💌 from NxCloud.

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.