Skip to content
Back

script "build" was terminated by signal SIGKILL (Forced quit)

  • 0
  • Self Hosted
  • Sites
faye
17 Dec, 2025, 20:38

Heyo,

For some reason, my Next.js 16.0.10 version does not build properly. Here is the last logs:

TypeScript
1063 packages installed [22.54s]
$ next build
No build cache found. Please configure build caching for faster rebuilds. Read more: https://nextjs.org/docs/messages/no-cache
Next.js 16.0.10 (Turbopack)
   - Experiments (use with caution):
     · clientTraceMetadata
     ✓ rootParams
     · swcPlugins

   Creating an optimized production build ...
Compiled successfully in 10.5min
[@sentry/nextjs - After Production Compile] Info: Sending telemetry data on issues and performance to Sentry. To disable telemetry, set `options.telemetry` to `false`.
[@sentry/nextjs - After Production Compile] Warning: No auth token provided. Will not upload source maps. Please set the `authToken` option. You can find information on how to generate a Sentry auth token here: https://docs.sentry.io/api/auth/
Completed runAfterProductionCompile in 3369ms
error: script "build" was terminated by signal SIGKILL (Forced quit)
bash: line 1:    40 Killed                  bun run build

No idea what to do else here.

TL;DR
Developers encountering "script 'build' was terminated by signal SIGKILL (Forced quit)" error while trying to build a Next.js 16.0.10 version. The issue may be related to a forced quit during the build process. One possible solution could be to check system resources like memory and CPU usage during the build to ensure that there are no constraints causing the forced quit. Additionally, reviewing the configuration for build caching could help in speeding up rebuilds.
Reply

Reply to this thread by joining our Discord

Reply on Discord

Need support?

Join our Discord

Get community support by joining our Discord server.

Join Discord

Get premium support

Join Appwrite Pro and get email support from our team.

Learn more