Is this a regression?

Yes

Description

One of the dependencies in spectator, namely replace-in-file, has been using very outdated packages that would likely need some migration but ultimately make the package more stable and probably improves performance as well.

Right now it uses a really old version of glob that is 3 years old and no longer supported.

If updating the dependency is still blocked, can we at least override the sub-dependencies in order to make sure we get rid of some of the more demanding deprecation messages?

Please provide a link to a minimal reproduction of the bug

No response

Please provide the exception or error you saw

various deprecation messages on `npm install`

Please provide the environment you discovered this bug in

Latest on Windows

Anything else?

Looking at projects/spectator/package.json (current link)

@testing-library/dom has version 10.4.0 out, compared to 8.11.0 from 7 months ago
jquery is still at 3.7.1 and is fine
tslib is at version 2.8.1 compared to 2.6.2 in project, though it would likely still pick latest
replace-in-file however is at version 8.3.0 now from 2 months ago, where spectator still uses (hardcoded) 6.2.0 from 4 years ago.

Seeing that it is hardcoded, there's probably a reason to do that but I think its time to make sure the project is not using those acient packages anymore. Especially seeing how many are outdated. I can only speculate that it happened because of some bug when migrating the project to Angular 12, but I would hope that some time could be spent making sure that the project is compatible with latest versions or replace them with new solutions that do work.

Do you want to create a pull request?

No