fix(js): not generate tsconfig if already exists

[xiongemi]

Current Behavior

• in serve target, it uses executor @nx/webpack:dev-server
• in packages/webpack/src/executors/dev-server/dev-server.impl.ts, when buildLibsFromSource is false, it calls createTmpTsConfig to create a temp config
• in webpack.config.js, it has module.exports = composePlugins(withNx(). in withNx, it calls NxTsconfigPathsWebpackPlugin.
• when buildLibsFromSource is false, it called createTmpTsConfig again based on the temp config. it created an infinite loop because it creates a tsconfig that extends itself.

Expected Behavior

• do not create a temp config if it is a generated ts config

Related Issue(s)

Fixes #28006

[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)		Dec 12, 2024 2:08am

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit f436fde. 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=lint,test,build,e2e,e2e-ci --base=0d1c96085e7b10fde47e3b12dd3f2b50b8f667fe --head=f436fde2472dc201c34d8cdfc85ad3f705e27e7c --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx-cloud conformance:check
• nx-cloud record -- nx format:check --base=0d1c96085e7b10fde47e3b12dd3f2b50b8f667fe --head=f436fde2472dc201c34d8cdfc85ad3f705e27e7c
• nx-cloud record -- nx sync:check
• 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.