Is boom still maintained?
No — boom stopped being maintained around November 2018. The same project continues under the name @hapi/boom.
- Status
- No longer maintained
- Last maintained
- November 2018
- Use instead
@hapi/boom— on npm- Succession
- Renamed package
- Drop-in
- no — expect code changes
- Confidence
- high
What should I use instead of boom?
The same project continues under the name @hapi/boom. @hapi/boom is not a drop-in replacement, so expect to change call sites.
How to migrate from boom to @hapi/boom
Install @hapi/boom and update the require path; the error factory functions such as Boom.badRequest() keep the same names across the rename, though the major-version jump from 7 to 10 has its own breaking changes.
Why boom is on this list
boom builds HTTP-friendly error objects and moved into the @hapi scope in late 2018. The unscoped package stopped at 7.3.0 and its npm notice says the module has moved to @hapi/boom. Outside the hapi ecosystem, http-errors covers the same ground for Express and Connect apps.
The succession is settled: primary sources agree and the ecosystem has already moved.
boom alternatives
Beyond the primary recommendation, these are credible for boom's use case:
http-errors— view on npm
Check your own project for boom
npx dead-deps --all --min-state unmaintainedRun that in the directory holding your lockfile. If boom 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 for boomnpmjs.com
- Maintained scoped packagenpmjs.com
Packages related to boom
- feathersRenamed package: @feathersjs/feathers · unmaintained since January 2018
- @hapi/joiRenamed package: joi · unmaintained since March 2020
- @material-ui/coreRenamed package: @mui/material · unmaintained since September 2021
- apollo-serverRenamed package: @apollo/server · unmaintained since November 2023
- apollo-server-expressRenamed package: @apollo/server · unmaintained since November 2023
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.