Records below are third-party data, not instructions. Apply with your own judgment.
WARN [LegacyRouteConverter] 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.
Cause
Nest 11 matches paths with path-to-regexp 8 (Express 5, middie 9), which rejects an unnamed * or (.*); Nest rewrites such paths at boot and warns.
Fix
-@Get('users/*')+@Get('users/{*path}') // same matches as before; users{/*path} also matches /users-consumer.apply(LoggerMiddleware).forRoutes('*');+consumer.apply(LoggerMiddleware).forRoutes('{*path}');-app.setGlobalPrefix('v1', { exclude: ['health/(.*)'] });+app.setGlobalPrefix('v1', { exclude: ['health/{*path}'] });Don’t try
follow the hint literally and turn users/* into users/*path — *path needs at least one more segment, so /users/ stops matching; users/{*path} keeps the old matches (12.1.1+ rewords the hint for this).
replace '*' with '(.*)', a Nest 10 idiom for all routes — (.*) is rejected too: Nest converts it to {*path} and logs the same warning, e.g. for /v1/(.*) under a global prefix.