-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(linter): cache --outputFile #6852
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/nrwl/nx-dev/Cc1ArRehNpUyY6qqihNT9CyCK4Gt [Deployment for 974aa50 canceled] |
Nx Cloud ReportCI ran the following commands for commit 974aa50. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this branch Sent with 💌 from NxCloud. |
bf99d26
to
820bdbf
Compare
820bdbf
to
a7dc035
Compare
a7dc035
to
4f28536
Compare
4f28536
to
974aa50
Compare
Could this change be a cause for #6957? It does seem that failures on cache read are happening only on lint tasks. |
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
When
--outputFile
is passed for ESLint projects, Nx does not properly cache the output file.Expected Behavior
The
--outputFile
is cached by Nx.Related Issue(s)
Fixes #