fix(js): invalidate tsconfig files cache in the @nx/js/typescript plugin when extended files change

[leosvelperez]

Current Behavior

• The persistent tsconfig files cache used by the @nx/js/typescript plugin does not get invalidated when the tsconfig files it extends from are updated.
• Absolute paths are stored in the cache, which would be incorrect when distributing the cache.
• The plugin throws a cryptic error when the lock file doesn't exist.

Expected Behavior

• The persistent tsconfig files cache used by the @nx/js/typescript plugin should get invalidated when the tsconfig files it extends from are updated.
• Paths should be stored relative to the workspace root.
• The plugin should handle when the lock file is missing.

Additionally, a few other performance improvements were made to offset the overhead introduced by creating a stricter cache key:

• cache and reuse file reads between tsconfig reads and file hashing (now each file is only read once, if read at all)
• initialize a pre-populate tsconfig files cache in a first pass to skip checking cache entries' key in subsequent reads
• reduce the tsconfig file cached content we store to disk
• cache the check for external project references

Related Issue(s)

Fixes #29429

[vercel]

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

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Feb 18, 2025 10:25am

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 6d9ad6b.

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e,e2e-c...	✅ Succeeded	36m 6s	View ↗
nx run-many -t check-imports check-commit check...	✅ Succeeded	16s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	2s	View ↗
nx-cloud record -- nx format:check --base= --he...	✅ Succeeded	7s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	5s	View ↗
nx documentation	✅ Succeeded	1m 51s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-02-18 11:05:06 UTC

[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.