I have tested this item ? unsuccessfully on b12d4eb

This is not correct.
You must do a full npm and composer install when you do these updates as there are files that might get updated by other scripts when dependencies are updated.

For example tinmyce and codemirror where the version number in the plugin is updated

Not sure why this is not part of the update command @dgrammatiko ?

rpm run update:

Edit: you need to manually bump the package.json versions and then run the command above IIRC

Thanks, fixed it

Something is wrong here. The vue package is a hard dependency, but I can't find it as a full package in the package-lock.json.

In any case, since this PR already contains those updates, I'm closing #41451 and #41455.

There are over 7'000 removald un the package lock file in this pr. Not sure if this has something to do with a never npm version since I did it last time.

I tried and built #41545 for comparison

@brianteeman which npm version did you use?

I'v just did a fresh install of the package from drone and all works. Nothing indicates that there is an error in an asset. Also the system tests are running through, when they do not hit the timeout.

@brianteeman which npm version did you use?

8.19.2

@laoneo could you restore the indentation to 2 spaces instead of 4 for the package.json and the lock file?

Reverted the last commit

@brianteeman which npm version did you use?

8.19.2

That might be the issue as I'm on 9.6.7.

@dgrammatiko gets the same effect, so we are fine with this pr here as I do mainly the updates

FWIW it's time to push node/npm as 16 that we are currently have as minimum goes EOL in few weeks. It's on my todo list

But I would do it on 5.0 then only.