Thanks for the PR, @JoshuaKGoldberg!

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!

Name	Link
🔨 Latest commit	518dff3
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/656078b5000bc700084e87fe
😎 Deploy Preview	https://deploy-preview-7988--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 96 (🟢 up 5 from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 98 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify site configuration.

Could we just add nx as a dep and then prefix with yarn instead?

Swapping "start": "npx nx start" with "start": "yarn nx start" yields:

josh ~/repos/typescript-eslint/packages/website $ yarn start
Usage Error: Couldn't find a script named "nx".

Same with yarn run nx start. I've been reading through https://nx.dev/core-features/run-tasks & co but don't see any recommendations around this?

cc @JamesHenry too

Yeah I'm not quite sure - I would have thought that yarn nx would run the locally installed verison of nx - do we need to add nx as a dependency to each and every package so that yarn can see it?

IDK how Yarn3 works - you didn't need to do that with yarn1 as it'd just look in the parent folder.

How frustrating yeah this definitely worked fine in yarn 1. FWIW you can also install nx globally one time and it will always work as well, it will resolve your most local installation possible before attempting to run the actually globally installed code.

I’ll need to play with this to get a real sense of what might optimal here, I’m afraid I lost all of the weekend because of moving apartments and my next availability will be this coming weekend, so feel free to do whatever makes the most sense in the immediate term if this is blocking