gitnubster
gitnubster
@igbaryyaAMD It looks solved for me with npm 10.5.0 / node 20.12.0 and 18.20.0
Might be a duplicate, see https://github.com/npm/cli/issues/7024 Does a second npm install work for you @stachupl stachup? Here it does, as a workaround.
@stachupl node 20.12.0/18.20.0 with npm 10.5.0 seem to have fixed this issue for me. Maybe the combination of the newer node versions help then? I cleared cache with -f, cleared...
Are there any updates on this issue? Thanks.