Definitely! I would love to hear what kind of replacements they had to make:

>As part of our goal to optimize dependencies, we also updated and/or replaced npm packages that were marked as deprecated by their authors – even when they were deeply nested in the dependency tree.

I wonder if they just rewrote some smaller packages themselves, or if they managed to find a maintained alternative for all of them?