Viktor Hedefalk

Plus one, this must have broken with a new release. I'm on 0.149.5 5321b10aa41e2ac0603c7a6fc99ba1ae9421b460 and it's just doing `//` in tsx.

Is any of the suggestions above working good for zsh? Seemed to be bash specific…? I still lean on npm to just help me with my own scripts in package.json....

I'm trying to poc using deno to create a standalone next.js executable with deno compile and I'm getting the same issue: I'm for now just using the latest next.js scaffold...

The next standalone init script looks like so: ```js const path = require('path') const dir = path.join(__dirname) process.env.NODE_ENV = 'production' process.chdir(__dirname) const currentPort = parseInt(process.env.PORT, 10) || 3000 const hostname...

Oh, some progress. The way next does is a great fit for the include-flag of course. Some progress: ``` deno compile --allow-all --unstable-ffi --output server2 --include ./.next/standalone/.next .next/standalone/server.cjs ./server2 ▲...

And also ``` TypeError: Cannot read properties of null (reading 'toUTCString') at Deno.stat.then.denoErrorToNodeError.syscall (ext:deno_node/_fs/_fs_stat.ts:149:32) at eventLoopTick (ext:core/01_core.js:175:7) ``` Sorry if I have derailed this issue to be specifically about running...

> [@hedefalk](https://github.com/hedefalk) Have you been able to compile a Next.js server in standalone mode in the end? no, not into something working.

>And if you really want to interact with the shell, you should pass -it as additional flags. I don't, I just want to run in foreground and be able to...

Just wanted to make sure this was nothing around sleep vs a "real usecase" so here's another very standalone service: ```Dockerfile FROM node:22 WORKDIR /usr/src/app RUN echo '{ \ "name":...

Huh, for docker the triple ctrl-c doesn't really stop the container, just the command. ``` 🐟 docker run express_server Server running on port 3000 ^C^C^C got 3 SIGTERM/SIGINTs, forcefully exiting...