fix(rollup): use workspace rootDir while compiling TS files

[kopach]

Fixes #11289

Tested this approach on real project using pnpm's patch mechanism

[vercel]

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

Name	Status	Preview	Updated (UTC)
nx-dev	✅ Ready (Inspect)	Visit Preview	Oct 24, 2023 2:43pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 486cab9. 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 -t e2e-macos --parallel=1 --base=f5eeb0aed63c6027b6e367e90ba9ecf72d7c6368 --head=486cab96a22d6e9829807139b78e4e755216e1d7

✅ Successfully ran 4 targets

• nx affected --targets=lint,test,build --base=f5eeb0aed63c6027b6e367e90ba9ecf72d7c6368 --head=486cab96a22d6e9829807139b78e4e755216e1d7 --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=f5eeb0aed63c6027b6e367e90ba9ecf72d7c6368 --head=486cab96a22d6e9829807139b78e4e755216e1d7
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[kopach]

hi @ndcunningham, could you, please, advice how can I handle the CI failing issue? I'ts not clear for me what exactly failing and why

[mandarini]

Hello @kopach ! I looked into this thoroughly and that PR is not achieving the desired behaviour. What is described in the issue, is that if the build target name is something else, then Nx does not identify the library as buildable, so this is the issue that should be addressed.

I will be closing this PR, but thank you very much for contributing! Let me know if you have any concerns!

[kopach]

Ok, sure @mandarini . No problem. It's just something which solves my issue (which has exact error output as described). I'm patching nx locally and it does the trick for me

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