Package management is impossible. When a big enough package pushes an update the house of cards eill fall. This causes project packages with greatly outdated versions to exist in production because there is no budget to diagnose and replace packages that are no longer available when a dependency requires a change.
Examples: adminJs or admin bro... one of them. Switched the package used to render rich text fields.
React-scripts or is it create react app, I don't recall. Back end packages no long work as is on the front end. Or something like that? On huge projects, who's got the budget to address this to get the project up to date?
This has to be a world wide thing. There is way to many moving targets for every company to have all packages up to date.
It's only a matter of time before an exploit of some sort is found and who knows what happens from there.
That's basically what happened with log4j or whatever that java bug was a few years ago. A lot of things still haven't been patched.
Package management is impossible. When a big enough package pushes an update the house of cards eill fall. This causes project packages with greatly outdated versions to exist in production because there is no budget to diagnose and replace packages that are no longer available when a dependency requires a change.
Examples: adminJs or admin bro... one of them. Switched the package used to render rich text fields.
React-scripts or is it create react app, I don't recall. Back end packages no long work as is on the front end. Or something like that? On huge projects, who's got the budget to address this to get the project up to date?
This has to be a world wide thing. There is way to many moving targets for every company to have all packages up to date.
It's only a matter of time before an exploit of some sort is found and who knows what happens from there.
That's basically what happened with log4j or whatever that java bug was a few years ago. A lot of things still haven't been patched.