opensource-joe commented on issue #442: URL: https://github.com/apache/fineract-backoffice-ui/issues/442#issuecomment-5397848407
@Aman-Mittal, I tried this, and it still doesn't resolve as written. Here are a few notes before I spend more time on it. The two-command split cannot work. `@angular/[email protected]` declares `"@angular/compiler": "22.0.7"` as an exact peer, so moving the seven runtime packages first breaks it before the second command runs. A tenth package is also in the way. `@angular-architects/[email protected]` declares `"@angular/build": "~22.0.0"`, so `@angular/[email protected]` needs it on 22.1.x. Its `^22.0.6` already permits 22.1.1, so package.json needs no change for it, only the lockfile. The real blocker is that npm will not get there incrementally. From a clean `node_modules`, I tried the two commands verbatim, all nine at `^22.1.0`, all nine pinned exactly, all ten named in a single `npm install`, and dropping `@angular/build` from the set. All ERESOLVE. Deleting `package-lock.json` and regenerating resolves with zero errors, so the dependency set is fine, but that is an 11,587-line lockfile diff. Two questions: Is a regenerated lockfile acceptable here, or would you rather this wait for something cleaner? And what npm does CI run? I am on 11.17.0 with 12.0.2 available, and if they resolve differently, that would explain all of the above. One smaller thing: `^22.1.0` floats to 22.1.3, so `--save-exact=false` will not land 22.1.0 in the lockfile. Exact pins would. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
