Is lodash.get still maintained?
No — lodash.get stopped being maintained around August 2016. optional chaining (?.) 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
- August 2016
- Use instead
optional chaining (?.)- Succession
- Absorbed elsewhere
- Drop-in
- not applicable
- Confidence
- high
What replaced lodash.get?
optional chaining (?.) 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.get to optional chaining (?.)
get(obj, 'a.b.c', fallback) becomes obj?.a?.b?.c ?? fallback. If the path is only known at runtime, keep get from the full lodash package instead.
Why lodash.get is on this list
The single-method lodash.get package was last published in August 2016 and now carries a deprecation notice from the lodash maintainers reading "This package is deprecated. Use the optional chaining (?.) operator instead." Optional chaining is supported in every maintained Node version and browser. The per-method lodash.* packages as a group are no longer being updated.
The succession is settled: primary sources agree and the ecosystem has already moved.
lodash.get alternatives
Beyond the primary recommendation, these are credible for lodash.get's use case:
lodash— view on npm
Check your own project for lodash.get
npx dead-deps --all --min-state unmaintained
Run that in the directory holding your lockfile. If lodash.get 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.getnpmjs.com
- MDN: optional chaining operatordeveloper.mozilla.org
Packages related to lodash.get
- lodash.isequalReplaced by node:util.isDeepStrictEqual in the platform · unmaintained since January 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
- qReplaced by Promise (native) in the platform · unmaintained since October 2017
- 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.