Open p3x-robot opened 2 months ago
The ng version
output indicates that you're on 18.1.0
, which is the current latest. So I think the message is accurate.
What exactly is ncu
? Is that npm-check-updates
? Based on:
Run ncu -u to upgrade package.json
I'm guessing it updated your node_modules
but not the package.json
? I think ng update
checks the currently installed version, not the one referenced in package.json
. If you reinstall a fresh copy of node_modules
and update without ncu
it should run as expected: rm -rf node_modules/ && npm ci && ng update @angular/core @angular/cli
.
ncu just runs the check to see if there are updates for dependencies listed in package.json. Running it with -u only updates package.json and to actually install the updates, user needs to run npm install themself.
So guess the problem OP has is that two different tools that should check the same package.json file are giving different answers. (Or maybe ncu checks node_modules, and that would explain the difference.)
Angular checks node_modules/
. If the node_modules/
versions are 18.1.x (which is implied from the ng version
output), then I think this is working as intended.
Which @angular/* package(s) are the source of the bug?
upgrade
Is this a regression?
Yes
Description
Please provide a link to a minimal reproduction of the bug
try to update and it says "We analyzed your package.json and everything seems to be in order. Good work!"
Please provide the exception or error you saw
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
No response