Replace express examples with h3

[Barbapapazes]

Documentation is

• Missing
• Outdated
• Confusing
• Not sure?

Explain in Detail

Hello,

Since express is widely outdated in many way (no support for async and await, no update since a while and a v5 still in bêta avec more than 9 years, I think that we could use h3 for this job.

In fact, h3 is very low level, moderne and way more efficient that express.

Your Suggestion for Changes

Still in progress because examples could become more complexe by using this layer

Reproduction

No response

Steps to reproduce

No response

[patak-dev]

Even if I think h3 (or fastify?) should be promoted, I don't know if it is bad to keep express in our docs a bit more. Maybe we could add a note that we are using express because it is simple and the API is known by more devs, but users are expected to use a modern alternative.

[Barbapapazes]

Even if I think h3 (or fastify?) should be promoted, I don't know if it is bad to keep express in our docs a bit more. Maybe we could add a note that we are using express because it is simple and the API is known by more devs, but users are expected to use a modern alternative.

Yes, that could be a great first move! Indeed, I agree that the api provided by express is the most easier and the one from fastify or h3 is more difficult for a new dev.

[Shyam-Chen]

import fastify from 'fastify';
import middie from '@fastify/middie';

// ...

  const app = fastify();

  await app.register(middie);

// ...

  app.use(vite.middlewares);

[rexhent]

Even if I think h3 (or fastify?) should be promoted, I don't know if it is bad to keep express in our docs a bit more. Maybe we could add a note that we are using express because it is simple and the API is known by more devs, but users are expected to use a modern alternative.

Would having both be appropriate?