vite.createServer() exits if process.env.CI != 'true'

Describe the bug

Today I spent a few hours tracking down some odd behavior in vite. I was using the dev server middleware like this:

        const vitemw = await vite.createServer({
            server: { middlewareMode: 'html' }
        })

When I ran this within docker-compose run it worked, but when I used docker-compose up it would just immediately exit:

app0_1     | > node ./src/serve.js dev
app0_1     |
app0_1     | starting server; mode: dev
app0_1     | > Ready on localhost:3000~!
x_app0_1 exited with code 0

It turns out this was because of this block from vite:

    if (process.env.CI !== 'true') {
        process.stdin.on('end', exitProcess);
        process.stdin.resume();
    }

I suggest removing this block, as a middleware should not be causing a program exit in any case. It’s also undesirable behavior, since it may be running in a process with no stdin.

At the very least it shouldn’t die silently.

Reproduction

I think the snippet above makes it clear why this happens.

System Info

System:
    OS: Linux 5.11 Ubuntu 21.04 (Hirsute Hippo)
    CPU: (8) x64 Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz
    Memory: 852.02 MB / 15.29 GB
    Container: Yes
    Shell: 5.1.4 - /bin/bash
  Binaries:
    Node: 15.11.0 - ~/.fnm/current/bin/node
    npm: 7.6.0 - ~/.fnm/current/bin/npm
  Browsers:
    Chrome: 91.0.4472.77
    Firefox: 89.0
  npmPackages:
    vite: ^2.4.1 => 2.4.1

Used Package Manager

npm

Logs

n/a

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a Vite issue and not a framework-specific issue. For example, if it’s a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/vue-next instead.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.

[akvadrako]

Thanks for the quick fix 😃

[IanVS]

@xhlsrj, are you running vite in middleware mode? Have you tested with vite 2.4.2? I believe it should work for you, since it includes #4082 as mentioned.