get stuck when building nextjs project with deno, and why does it will start the nodejs process?

[BertramYe]

when I build my current project with the commend here below, I found that I was just get stuck for a long time (over 5 mins), and there were not any logs or output in the terminal, how can I get the building logs and found out what actually happened?

os: Ubuntu 24.04.3 LTS
nextjs : 16.1.1
deno 2.6.3+7222e85 (canary, release, x86_64-unknown-linux-gnu)
v8 14.2.231.17-rusty
typescript 5.9.2

when I run the commend below:

$ deno run build

and it just get stuck (over 5mins) without any return or output, and then I get the content here below::

and when I check its error logs, it shows just like below:

and just from the issue, which should be caused by the file, but it didn't show any lacked file or directory path/name

how can I resolve this issue? it seems that it need the nodejs to be installed, as it shows spawning node pooled process, why dose this happend? and why it will start/running the node pooled process?

---------------------------
creating new process

Caused by:
- spawning node pooled process
- No such file or directory (os error 2)

Debug info:
- Execution of get_written_endpoint_with_issues_operation failed
- Execution of PlainIssue::from_issue failed
- Execution of PlainSource::from_source failed
- Execution of <WebpackLoadersProcessedAsset as Asset>::content failed
- Execution of WebpackLoadersProcessedAsset::process failed
- Execution of evaluate_webpack_loader failed
- creating new process
- spawning node pooled process
- No such file or directory (os error 2)

[BertramYe]

and by the way, in this situation， I found the only solution is to install the nodejs and then do the rebuild, but I just want to use the deno to make my project go faster and decrease the consumption of resources, but now I have to install the nodejs and deno as the same times now, so why should I use the deno to host my nextjs project with the deno and nodejs installed sametime and running, instand of the nodejs only? I just want to all in for the pure deno, but feel a bit so sad, and weird.

and also by the way, if someone like me have the same issue (when building, just get stack and then failed), don't forget to use the commend here below to check weather your backend deno build get stuck:

# check the weather running process get stuck or not
$ ps -aux | grep deno

# if you do , kill  the process manually
$ kill -9 [your-deno-building-process-id]

otherwise you can't build it with the error like below: