feat(core): support rollup.config.ts

[ThePlenkov]

I would like to be able to use rollup.config.ts. Same way it's used by rollup and vite teams too.

Current Behavior

Currently nx plugin does not reconize project containing rollup.config.ts. It expects only {c|m}js files

Expected Behavior

When project has rollup.config.ts rollup plugin infers build target automatically. This build target should be able to find the rollup.config.ts. For that purpose a special configPlugin CLI parameter should be used

Related Issue(s)

Feature request #28226

[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	Dec 11, 2024 4:04pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 27a6d55. 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=6434ab3da359a10aa0173d40c0a9ddbe5b3d0349 --head=27a6d5527a0f1474ebde71d2a1b85d4ede71f044 --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=6434ab3da359a10aa0173d40c0a9ddbe5b3d0349 --head=27a6d5527a0f1474ebde71d2a1b85d4ede71f044
• nx-cloud record -- nx sync:check
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[ThePlenkov]

I had to revert forced --configPlugin @rollup/plugin-typescript because it breaks tests for rollup.config.js. Instead I made it optional. I analyze detected config path extension. If it's ts - then we load typescript config plugin, otherwise we just load the config as is.

[ThePlenkov]

it says pipeline is cancelled. I do not see any error logs..

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