2 Commits

Author	SHA1	Message	Date
Jack Hsu	09ebf5f2da	fix(eslint): ensure that packages in the same group as updated together (#30187) ... This PR updates `migrations.json` for `@nx/eslint` and `@nx/angular` so that `@typescript-eslint/*` and `@angular-eslint/*` packages that are installed in the workspaces are updated to the same version. I've updated it for v20 and v19, but if we need to go back further we could. This will also require patch versions for each major that we want to fix. **Note:** Previously there were two entries for `@nx/esilnt@20.4.0` that handles cases where one of `typescript-eslint` or `@typescript-eslint/eslint-plugin` are > 8. The packages in both entries overlap, so I collapsed them down to one entry that checks `typescript-eslint > 8`. ## Current Behavior If user has `@typescript-eslint/rule-tester` or `@angular-eslint/test-utils` installed, our migrations do not update these versions. This makes them out of sync with `@typescript-eslint/utils`, etc. which can lead to problems. ## Expected Behavior Packages in the same `@typescript-eslint/*` and `@angular-eslint/*` are updated together. If they are not installed, we don't add them to the workspace. ## Related Issue(s) <!-- Please link the issue being fixed so it gets closed when this is merged. --> Fixes #	2025-02-26 14:07:03 -05:00
Isaac Mann	84387f3611	feat(nx-dev): generate migration detail pages (#29580) ... Generates list of migrations on the plugin overview page and a standalone `/migrations` page. To add sample code changes for a migration that has an implementation file, create a `.md` file with the same name as the implementation file in the same folder as the implementation file. i.e. `move-cache-directory.md` for `move-cache-directory.ts`. Migrations that have `packages` defined will have a table generated with the package updates listed. Separate PRs will be created to add sample code changes for each migration with an implementation. The migration list on the plugin overview page: [Angular migrations](https://nx-dev-git-docs-migration-details-nrwl.vercel.app/nx-api/angular#migrations) Standalone migration list page: [Angular migrations](https://nx-dev-git-docs-migration-details-nrwl.vercel.app/nx-api/angular/migrations) Sample migration with added markdown file details: [17.0.0-move-cache-directory](https://nx-dev-git-docs-migration-details-nrwl.vercel.app/nx-api/nx#1700movecachedirectory) Sample migration with only package updates: [Angular 20.4.0](https://nx-dev-git-docs-migration-details-nrwl.vercel.app/nx-api/angular#2040packageupdates) Sample migration without any markdown file details: [update-angular-cli-version-19-1-0](https://nx-dev-git-docs-migration-details-nrwl.vercel.app/nx-api/angular#updateangularcliversion1910) - This last sample is very bare-bones and the reason why we need these pages in the first place. People don't know what migrations are actually doing. Follow up PRs will address pages like this.	2025-01-27 13:17:36 -05:00