Is handeling evething in one route antipattern?

[ivanjeremic]

I have some specific use cases where I serve multiple things with nitro, one of them being a nextjs app where I manually handle next and give it to the nitro eventHandler, because it would simplify things a lot I wanted to ask if it is an antipattern to have everything in one spread [...].tsroute handled and if it impacts performance? If there is something I could do better I would love to hear suggestions. Thanks.

const dev = process.env.NODE_ENV !== "production";
const app = next({ dev, dir: "./ui/nextjs" });
const handle = app.getRequestHandler();

export default eventHandler((event) => {

  if(event.path.includes("admin")) {
    return app
    .prepare()
    .then(() => {
      return handle(event.node.req, event.node.res);
    })
    .catch((error) => {
      throw error;
    });  
  }
  
  if(event.path === "/") {
    // return something different
  }

  if(event.path === "/xyz") {
    // return something for xyz
  }
});

```

[airtonix]

yes.

question asked another way:

• Are god components an anti pattern?
• Why are more files rather than less files useful in software projects?