-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore: fix cyclic dependency in repo caused by generate-lib script changes #7603
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
Conversation
Thanks for the PR, @bradzacher! typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community. The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately. Thanks again! 🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint. |
✅ Deploy Preview for typescript-eslint ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Heh, I just started gettin this too - thanks for the fix. I'll defer to @JamesHenry as the Nx wiz.
(assuming the lockfile is fixed ofc)
or actually, @bradzacher this feels like a good thing to get in asap - I'm happy to just get it in sooner |
Yeah we can land it sooner then cycle back with James to investigate why this wasn't caught sooner by nx. I'm not going to be able to get to my laptop for around 2 hours - if you wanted it asap feel free to pull and fix the lock file for me :) |
Well I'm stumped...
|
Nuke a bitch and try again? That's my standard workflow for fixing yarn problems heh |
No juice :( |
4bec329
okay so I now have a fresh and clean |
GH statuses didn't update - but there was a netlify build flake. |
Overview
In #7535 I made a change to the script so that it used our
utils
package to type anESLint
call.This actually introduced a nx cyclic dependency crash into the repo - but it looks like this crash was never seen due to caching or something I guess?
However on a fresh machine if you ran
yarn
, then it'll cause yarn to attempt to do a fresh build after an install and then nx would fail withcc @JamesHenry - this behaviour is super weird!
This PR moves the script to the
repo-tools
folder so that it's an isolated leaf, fixing the cyclic dependency.