fix(misc): ensure swc transpiler process required files

[leosvelperez]

Current Behavior

When having @swc-node/[email protected] installed, loading a config (or similar files needing transpilation in-process) might error complaining about invalid syntax or import statements used outside of a module.

This happens because, in version 1.8.0 of the @swc-node/register package, a fix was released where the utility now correctly uses the provided compiler options. The Nx helper to register the TS transpiler uses the @swc-node/register/read-default-tsconfig#readDefaultTsConfig to read those compiler options, and that utility returns an additional files property which, if present, is used by the @swc-node/register/register#register function to filter files out from processing. This is all fine, but while the Nx helper reads the compiler options (and hence the TS project files) from the provided tsconfig file (normally a project-specific one), it sets the SWC_NODE_PROJECT to the root tsconfig file. This means that before @swc-node/[email protected], the compiler options read from the project's tsconfig file were ignored and the root tsconfig file was always used, so effectively getting all files in the workspaces as part of the TS program. With @swc-node/[email protected] now the project's tsconfig file compiler options are used and only the files included in that tsconfig file are part of the program.

The above is not aligned with the ts-node transpilation, where the project's tsconfig file compiler options are correctly used, and the files are not a factor.

Expected Behavior

Loading a config (or similar files needing transpilation in-process) should work correctly.

Related Issue(s)

Fixes #21639
Fixes #21643

[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	Feb 7, 2024 3:18pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 31a6e4c. 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

---

🟥 Failed Commands
nx affected --target=e2e --base=2413e5daa53e961d13920cb1a71b0119efd4e5b1 --head=31a6e4c173c7852c29f2f408df570d7056bb4781 --parallel=1
nx affected -t e2e-macos --parallel=1 --base=2413e5daa53e961d13920cb1a71b0119efd4e5b1 --head=31a6e4c173c7852c29f2f408df570d7056bb4781

✅ Successfully ran 4 targets

• nx affected --targets=lint,test,build --base=2413e5daa53e961d13920cb1a71b0119efd4e5b1 --head=31a6e4c173c7852c29f2f408df570d7056bb4781 --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=2413e5daa53e961d13920cb1a71b0119efd4e5b1 --head=31a6e4c173c7852c29f2f408df570d7056bb4781
• nx documentation --no-dte

---

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.