Can't get setGlobalPrefix value in adapter

[Mittcio]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

In nest-application await this.httpAdapter?.init(); no options is passed from nest app to adapter

async init() {
        await this.httpAdapter?.init();

Minimum reproduction code

https://github.com/nestjs/nest

Steps to reproduce

No response

Expected behavior

To pass to adapter this.config

async init() {
        await this.httpAdapter?.init(this.config);

and in adapter will be able to call this.config.getGlobalPrefix();

Package

• I don't know. Or some 3rd-party package
• @nestjs/common
• @nestjs/core
• @nestjs/microservices
• @nestjs/platform-express
• @nestjs/platform-fastify
• @nestjs/platform-socket.io
• @nestjs/platform-ws
• @nestjs/testing
• @nestjs/websockets
• Other (see below)

Other package

No response

NestJS version

latest

Packages versions

latest

Node.js version

20

In which operating systems have you tested?

• macOS
• Windows
• Linux

Other

No response

[micalevisk]

I didn't get if this is a bug report or a feature request

[kamilmysliwiec]

Why do you need that?

[Mittcio]

The middleware in express way not work well, it has other aproach. And for that, I need to make some custom createMiddlewareFactory, because the path of middlewares already contains here the setGlobalPrefix and i need it to compare path

    createMiddlewareFactory(requestMethod) {
      retrun (...args) => {
         // some magic but path is /api/test and not /test
         this.middlewares.push(args)
      } 
   }

[Mittcio]

And here

get(...args) {
        // magic with middleware, filter middleware by path
       const m = this.middlewares.filter()
        return this.injectRouteOptions(common_1.RequestMethod.GET, ...args, m);
    }

Now all work well but i hardcode that prefix api that is not nice.

[Mittcio]

Not only I need, you also need it for example you pass extra param in public setErrorHandler(handler: Function, prefix?: string) :)

[Mittcio]

Here you (are forced to) pass prefix but it is not needed (may be because other adapter need it, fastyfy I don't see it)

nest/packages/platform-express/adapters/express-adapter.ts

Line 269 in 238d51d

public registerParserMiddleware(prefix?: string, rawBody?: boolean) {

public registerParserMiddleware(prefix?: string, rawBody?: boolean) {
    const bodyParserJsonOptions = getBodyParserOptions(rawBody!);
    const bodyParserUrlencodedOptions = getBodyParserOptions(rawBody!, {
      extended: true,
    });

    const parserMiddleware = {
      jsonParser: express.json(bodyParserJsonOptions),
      urlencodedParser: express.urlencoded(bodyParserUrlencodedOptions),
    };
    Object.keys(parserMiddleware)
      .filter(parser => !this.isMiddlewareApplied(parser))
      .forEach(parserKey => this.use(parserMiddleware[parserKey]));
  }

[Mittcio]

a ha ha ha, nice in adapter i can do

public registerParserMiddleware(prefix?: string, rawBody?: boolean) {
  this.prefix = prefix;
  // other code
}

or in setErrorHandler