npm / npm/cli

[BUG] npm error Exit handler never called! in next.js app

Open
#8,404 4 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug Needs Triage
Dominant language
JavaScript
Stars
10.1k
Forks
4.7k
Avg merge
2d 2h
Merged PRs (30d)
19

Description

Is there an existing issue for this?
  • I have searched the existing issues
This issue exists in the latest npm version
  • I am using the latest npm
Current Behavior

Hi!

I'm currently using the latest LTS version of Node.js (Node: 22.17.0 & npm: 10.9.2) and I'm getting an error when trying to build my Next.js v15.3.3 app project.

I've already tried:

  1. Deleting the package-lock.json file
  2. Removing the node_modules folder
  3. Cleaning the cache using:
npm cache clean --force

Here's the error I get when trying to build my app:

npm error Exit handler never called!
npm error This is an error with npm itself. Please report this error at:
npm error   <https://github.com/npm/cli/issues>
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-06-30T18_01_53_207Z-debug-0.log

Error: `npm ci` command failed.

You can also try deleting your `package-lock.json` file and run `liara deploy` again.
Expected Behavior

this is my expected Behavior

> next build

   ▲ Next.js 15.3.3

   Creating an optimized production build ...
   Linting and checking validity of types ...
   Collecting page data ...
   Finalizing page optimization ...
   Collecting build traces ...


Steps To Reproduce
Environment
  • npm: 10.9.2
  • Node.js: 22.17.0
  • OS Name: windows 11 Pro

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report names npm ci, Node.js 22.17.0, npm 10.9.2, Next.js 15.3.3, and a debug log at /root/.npm/_logs/2025-06-30T18_01_53_207Z-debug-0.log; start by reproducing the Windows 11 build or deploy command and inspecting that log. Establish a minimal reproduction with complete steps, then verify that npm ci and next build complete without the exit-handler error.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, next.js, nodejs
Domain
cli, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.