chore: update nx config to latest

[JamesHenry]

Hi Kent 👋

Hope you're doing well! I saw you recently upgraded to the latest nx, which is great, but it seems our automated migrations didn't run for you. If you run npx nx migrate latest instead of manually bumping the packages it allows nx to migrate your workspace to the latest and greatest automatically.

I've applied those changes here and a couple of clean up items. Additionally, we have a bunch of AI features these days (MCP server for your workspace, self-healing CI via our cloud AI agent etc) that I'm sure would be right up your street, and so just let me know if you'd like to have a brief catch up sync where I can demo them for you.

Cheers,

James

[JamesHenry]

Removing this outdated package (fully replaced by @nx/eslint that you already have) allowed a lot to be cleaned up from your lock file as you can see

[kentcdodds]

Thank you! Hopefully this fixes the release so it actually updates the version in the package.json as well. The last release pushed the package versions as they appear in the source which is not desirable 😅

I appreciate your help! How did you know I updated?

[JamesHenry]

@kentcdodds Yes, there was a breaking change in versioning config between the major versions that you updated (we now support updating more than one package.json (e.g. source and dist) in the same versioning run):

nx migrate would have migrated your config for you in this case

How did you know I updated?

I just had a note to myself to check in with you as it had been a while, so just a happy coincidence 😄

[nx-cloud]

View your CI Pipeline Execution ↗ for commit dc25759

Command	Status	Duration	Result
nx run-many --target build	✅ Succeeded	2s	View ↗
nx run-many --target typecheck	✅ Succeeded	1s	View ↗
nx lint	✅ Succeeded	1s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-09-23 23:04:53 UTC