> a global find & replace is... kinda trivial to do in most editors.
Global find & replace isn't a real solution here. For example, if I'm reviewing someone else's code, it's harder for me to verify that they didn't miss an import.
In general, anything that replaces a single source-of-truth (packages.json) with a process (“run find-and-replace with this query”) will increase the amount of energy spent on being vigilant about that process at the expense of other things.
Global find & replace isn't a real solution here. For example, if I'm reviewing someone else's code, it's harder for me to verify that they didn't miss an import.
In general, anything that replaces a single source-of-truth (packages.json) with a process (“run find-and-replace with this query”) will increase the amount of energy spent on being vigilant about that process at the expense of other things.