Fastify Adapter setGlobalPrefix exclusions no longer support parameters or wildcard Warning #14909
Description
Did you read the migration guide?
- I have read the whole migration guide
Is there an existing issue that is already proposing this?
- I have searched the existing issues
Potential Commit/PR that introduced the regression
No response
NestJS version
10->11.0.2->11.0.3
Describe the regression
After migrating to nest 11 using fastify setting a global prefix throws a warning
[08:50:28.633] WARN: Unsupported route path: "/api/*". 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...
[08:50:28.633] WARN: Unsupported route path: "/api/*". 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...
I test the latest release 11.0.3 and still the same issue
Minimum reproduction code
https://github.com/invaderb/nest-11-test
Input code
const globalPrefix = '/api';
app.setGlobalPrefix(globalPrefix);Expected behavior
no warnings to be thrown if setup correctly
Other
No response