Weird no space left error when pushing nextjs app

When I push small nextjs app I get this error:

 gzip: stdout: No space left on device
   /usr/bin/tar: /tmp/output-cache: Wrote only 4096 of 10240 bytes
   /usr/bin/tar: Child returned status 1
   /usr/bin/tar: Error is not recoverable: exiting now
   : exit status 2

4096 MB is the disk_quota I've assigned in manifest.yml and if I change it to fe. 2048MB, the error also changes to "Wrote only 2048 of 10240 bytes".
Is it meant to mean "of 10240 megabytes"? Even if so, why would a small js app (~400MB with node modules and build) need 10GB od space?

What version of Cloud Foundry and CF CLI are you using? (i.e. What is the output of running cf curl /v2/info && cf version?
cf8.exe version 8.7.3+efd1d03e7.2023-09-12

What version of the buildpack you are using?
1.8.13

If you were attempting to accomplish a task, what was it you were attempting to do?
execute cf push

What did you expect to happen?
successful execution of cf push

What was the actual behavior?

 gzip: stdout: No space left on device
   /usr/bin/tar: /tmp/output-cache: Wrote only 4096 of 10240 bytes
   /usr/bin/tar: Child returned status 1
   /usr/bin/tar: Error is not recoverable: exiting now
   : exit status 2

Can you provide a sample app?
No, but it's a simple next.js app with only few dependencies.

Please confirm where necessary:

• [+] I have included a log output
• [+] My log includes an error message
• [+] I have included steps for reproduction

Start with the reported cf push output, the manifest.yml disk_quota values, and the listed Node.js buildpack and CF CLI versions. Reproduce the staging failure with a comparable Next.js app if possible, then determine whether the quota or the Wrote only ... of 10240 bytes message is incorrect. Done means the behavior is explained or corrected and verified during cf push.