Should middlewareMode: true be the default when appType: 'ssr' is used?

We can't because SvelteKit is going to use appType: 'ssr' without middleware mode, as they are using the Vite server as is.

How about we make only vite.createServer() to default to middlewareMode: true when appType: 'ssr'?

While we keep middlewareMode: false for $ vite dev when appType: 'ssr'.

So that SvelteKit (and others) can still use $ vite dev instead of vite.createServer().

(Btw. I really like replacing ssr with custom. It addresses my concerns.)

CC @aleclarson.

Should middlewareMode: true be the default when appType: 'ssr' is used?

We can't because SvelteKit is going to use appType: 'ssr' without middleware mode, as they are using the Vite server as is.

How about we make only vite.createServer() to default to middlewareMode: true when appType: 'ssr'?

I actually like that middlewareMode only defines if the server is controlled by Vite or not, and that appType controls the type of app but has nothing to do with who manages the server. Given that this is an API that only advanced users will need I think it is better to keep middlewareMode and appType orthogonal.

Actually, how about a vite.createDevMiddleware()?

Before:

if (process.env.NODE_ENV === 'production') {
  app.use(sirv(`./dist/client/`))
} else {
  const vite = await import('vite')
  viteDevServer = await vite.createServer({
    server: { middlewareMode: true },
  })
  app.use(viteDevServer.middlewares)
}

After:

if (process.env.NODE_ENV === 'production') {
  app.use(sirv(`./dist/client/`))
} else {
  app.use((await import('vite')).createDevMiddleware())
}

It's low priority and I'm personally fine with the current API. But I can see many to welcome such aesthetic improvement and Vite 3 is a nice opportunity for that.

How about we make only vite.createServer() to default to middlewareMode: true when appType: 'ssr'?
While we keep middlewareMode: false for $ vite dev when appType: 'ssr'.
So that SvelteKit (and others) can still use $ vite dev instead of vite.createServer().

That sounds confusing to me. I think it's better if it just always have the same value. I don't mind overriding the default value if needed. The question to me though is what is the better default and I think that generally false would be preferable

Actually, how about a vite.createDevMiddleware()?

It's not a compelling need, but it might be slightly nicer. I wouldn't be opposed to it as a follow-up

better to keep middlewareMode and appType orthogonal.

That sounds confusing to me

👍 Ok that makes sense. You're right, it's clearer to separate both. Sorry for the noise.

As for createDevMiddleware(), I still think that it looks nicer than (await createServer({ server: { middlewareMode: true } })).middlewares. It's only aesthetics so I'm fine if we skip that part, although I do think that such aesthetics do contribute to Vite's zero-config feeling in a non-negligible way. Folks (rightfully) dread verbose configurations a la webpack.

Anyways, LGTM; green-check-marking this.

I agree with you @brillout, it feels strange to use a createServer function that doesnt creates a server. Maybe createServerMiddlewares to keep them aligned. We can do another PR to discuss with others

Maybe createServerMiddlewares to keep them aligned.

👍

Although I have a slight preference for createServerMiddleware() without s since it's expected that a middleware may be composed of multiple middlewares. (And it's actually technically speaking accurate: the returned value is a single middleware function (req, res, next) (that uses several middleware functions).)