Is lodash.isequal still maintained?
No — lodash.isequal stopped being maintained around January 2017. node:util.isDeepStrictEqual covers this in the language or runtime now, so the right move is to delete the dependency rather than replace it.
- Status
- No longer maintained
- Last maintained
- January 2017
- Use instead
node:util.isDeepStrictEqual- Succession
- Absorbed elsewhere
- Drop-in
- not applicable
- Confidence
- high
What replaced lodash.isequal?
node:util.isDeepStrictEqual covers this in the language or runtime now, so the right move is to delete the dependency rather than replace it. There is no package to install; the dependency comes out and platform code goes in.
How to migrate from lodash.isequal to node:util.isDeepStrictEqual
isEqual(a, b) becomes require('node:util').isDeepStrictEqual(a, b) on the server. For browser bundles, dequal or fast-deep-equal are the usual small stand-ins.
Why lodash.isequal is on this list
lodash.isequal was last published in January 2017 and now carries a deprecation notice from the lodash maintainers reading "This package is deprecated. Use require('node:util').isDeepStrictEqual instead." That built-in has shipped with Node since version 9. The two are close but not identical: the Node version compares types and prototypes strictly.
The succession is settled: primary sources agree and the ecosystem has already moved.
lodash.isequal alternatives
Beyond the primary recommendation, these are credible for lodash.isequal's use case:
lodash— view on npmdequal— view on npmfast-deep-equal— view on npm
Check your own project for lodash.isequal
npx dead-deps --all --min-state unmaintained
Run that in the directory holding your lockfile. If lodash.isequal is anywhere in your tree — a direct dependency or buried under something else — it appears in the report with this verdict, this successor and the same evidence links, alongside anything else that has stopped moving. Nothing is uploaded; the scan reads your lockfile locally and queries public registry metadata.
Exit code 1 means something was flagged, which makes npx dead-deps --min-state deprecated usable as a CI gate. See how verdicts are produced.
Evidence
Every claim on this page traces to a primary source. Check them:
- npm deprecation notice on lodash.isequalnpmjs.com
- Node.js docs: util.isDeepStrictEqualnodejs.org
Packages related to lodash.isequal
- lodash.getReplaced by optional chaining (?.) in the platform · unmaintained since August 2016
- qReplaced by Promise (native) in the platform · unmaintained since October 2017
- bluebirdReplaced by Promise (native) in the platform · unmaintained since November 2019
- left-padReplaced by String.prototype.padStart in the platform · unmaintained since April 2018
- querystringReplaced by URLSearchParams in the platform · unmaintained since February 2021
See the full index of covered packages, or read the methodology for how a verdict is reached and why a quiet package is not a dead one.