Unsupported route path warning produced from app.setGlobalPrefix()

[0xHendrix]

Is there an existing issue for this?

• I have searched the existing issues

Current behavior

Setting a global prefix in Nest.js 11 produces the following warning:

Unsupported route path: "/v1/*". In previous versions, the symbols ?, *, and + were used to denote optional or repeating path parameters. The latest version of "path-to-regexp" now requires the use of named parameters. For example, instead of using a route like /users/* to capture all routes starting with "/users", you should use /users/*path. For more details, refer to the migration guide. Attempting to auto-convert... {"context":"LegacyRouteConverter"}

const app = await NestFactory.create(AppModule, { bufferLogs: true, rawBody: true });
app.setGlobalPrefix("/v1");

When I remove app.setGlobalPrefix("/v1") the warning goes away.

Minimum reproduction code

N/A

Steps to reproduce

Include a global prefix in your main.ts file:

const app = await NestFactory.create(AppModule, { bufferLogs: true, rawBody: true });
app.setGlobalPrefix("/v1");

Expected behavior

No warnings appear from setting a global prefix

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

11.0.5

Packages versions

[System Information]
OS Version : macOS24.3.0
NodeJS Version : v22.11.0
NPM Version : 10.9.0

[Nest CLI]
Nest CLI Version : 11.0.2

[Nest Platform Information
platform-express version : 11.0.5
microservices version : 11.0.5
schematics version : 11.0.0
passport version : 11.0.5
schedule version : 5.0.1
graphql version : 13.0.2
swagger version : 11.0.3
testing version : 11.0.5
apollo version : 13.0.2
common version : 11.0.5
config version : 4.0.0
axios version : 4.0.0
bull version : 11.0.1
core version : 11.0.5
cqrs version : 11.0.0
cli version : 11.0.2

Node.js version

22.11.0

In which operating systems have you tested?

• macOS
• Windows
• Linux

Other

No response

[micalevisk]

I didn't manage to reproduce it here on Linux.

import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';

async function bootstrap() {
  const app = await NestFactory.create(AppModule, {bufferLogs:true,rawBody:true});
  app.setGlobalPrefix("/v1");
  await app.listen(process.env.PORT || 3000);
}
bootstrap();

import { Module } from '@nestjs/common';
import { AppController } from './app.controller';

@Module({
  controllers: [AppController]
})
export class AppModule {}

import { Controller, Get } from '@nestjs/common';

@Controller()
export class AppController {
  @Get()
  foo() {
      return 1
  }
}

Please provide a minimum reproduction repository. You can start one by running npm init nest in your terminal

why reproductions are required

[micalevisk]

make sure you've read the migration guide

I only got that warning when using @Get("*"), which is expected.

[krlkm]

In my case, I have something like this:

  configure(consumer: MiddlewareConsumer) {
    consumer.apply(SomeMiddleware).forRoutes('*');
  }

So, /v1/* will trigger this warning.
Updating it to '*path' will fix the problem.

[susanta96]

Can you share any way that I can resolve this ?? Same issue I am gettting too many warning

configure(consumer:` MiddlewareConsumer) {
  consumer.apply(LoggerMiddleware).forRoutes('*');
}

[ikdi]

I have the same problem as @0xHendrix when use app.setGlobalPrefix

[kamilmysliwiec]

Just change * to {*path} as suggested in the migration guide https://docs.nestjs.com/migration-guide#express-v5