deep-equal is not only 2 orders of magnitude slower than fast-deep-equal, but it's by far the biggest dependency tree limbs in the project containing polyfills that haven't been needed for browsers or Node since 2015 (and your package.json denotes "node": ">= 14"). At 38M weekly downloads, it is not a small project either. Swapping dependencies to fast-deep-equal could save consumers kilobytes and reap a performance benefit. Transitive dependencies would go from 53 to 4.
deep-equal
is not only 2 orders of magnitude slower thanfast-deep-equal
, but it's by far the biggest dependency tree limbs in the project containing polyfills that haven't been needed for browsers or Node since 2015 (and yourpackage.json
denotes"node": ">= 14"
). At 38M weekly downloads, it is not a small project either. Swapping dependencies tofast-deep-equal
could save consumers kilobytes and reap a performance benefit. Transitive dependencies would go from 53 to 4.