fix(js): add {projectRoot} prefix to d.ts fileset in typescript plugin#35037
fix(js): add {projectRoot} prefix to d.ts fileset in typescript plugin#35037FrozenPandaz merged 3 commits intomasterfrom
Conversation
The typescript plugin was emitting a bare `**/*.d.ts` fileset input
without the required `{projectRoot}/` prefix, causing the Nx hasher
to warn: "**/*.d.ts does not start with {workspaceRoot}/"
✅ Deploy Preview for nx-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for nx-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
View your CI Pipeline Execution ↗ for commit 47ba086
☁️ Nx Cloud last updated this comment at |
The typescript plugin was emitting a bare `**/*.d.ts` fileset input
without the required `{projectRoot}/` prefix, causing the Nx hasher
to warn: "**/*.d.ts does not start with {workspaceRoot}/" [Self-Healing CI Rerun]
The typescript plugin was emitting a bare `**/*.d.ts` fileset input
without the required `{projectRoot}/` prefix, causing the Nx hasher
to warn: "**/*.d.ts does not start with {workspaceRoot}/" [Self-Healing CI Rerun]
There was a problem hiding this comment.
Nx Cloud has identified a flaky task in your failed CI:
🔂 Since the failure was identified as flaky, we triggered a CI rerun by adding an empty commit to this branch.
🔔 Heads up, your workspace has pending recommendations ↗ to auto-apply fixes for similar failures.
🎓 Learn more about Self-Healing CI on nx.dev
#35037) ## Current Behavior The TypeScript plugin emits a bare `**/*.d.ts` fileset input (without a `{projectRoot}/` prefix) for dependency file tracking. The Nx hasher expects all filesets to start with either `{projectRoot}/` or `{workspaceRoot}/`, so it logs a warning for every project: ``` NX **/*.d.ts does not start with {workspaceRoot}/. This will throw an error in Nx 20. ``` ## Expected Behavior No warning is emitted. The fileset correctly uses `{projectRoot}/**/*.d.ts` so the hasher knows it's scoped to the dependency project's root. ## Related Issue(s) N/A — discovered while debugging e2e test failures. (cherry picked from commit 6c92d92)
|
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. |
Current Behavior
The TypeScript plugin emits a bare
**/*.d.tsfileset input (without a{projectRoot}/prefix) for dependency file tracking. This was introduced in #34968. The Nx hasher expects all filesets to start with either{projectRoot}/or{workspaceRoot}/, so it logs a warning for every project:Expected Behavior
No warning is emitted. The fileset correctly uses
{projectRoot}/**/*.d.tsso the hasher knows it's scoped to the dependency project's root.Related Issue(s)
Fixes regression from #34968.