Route resolving fails when setGlobalPrefix() is used

Hi Shekohex, after some trial and error I think nest-router is having issues when a globalPrefix is set in bootstrap function.

Let’s say my routes look like this:

const routes:Routes = [
	{
		path: '/test', 
		module: TestBackendModule
	}
];

Combined with this

async function bootstrap() {
	const app = await NestFactory.create(AppModule);
	app.setGlobalPrefix(`api`);
	await app.listen(3333);
}

Neither calls to /api/test nor calls to /test could be routed successfully. After removing the call to setGlobalPrefix, calls to /test were routed to the TestBackendModule. Is this behaviour intended? If so, may I recommend to add a note to the Readme.

[willcooley]

Is there a workaround to this? Only thing I can think of fixing nest’s router, and keeping the package local until something is done. I’m in a tight squeeze to have this fixed by tomorrow. Any ideas? Is there anyway to override nest’s router method for the fix to be used, instead of using what is currently there? I’ve lost a bunch of time trying to figure this out sadly, lol.

[shekohex]

Fixed as of https://github.com/nestjs/nest/pull/1594 🎉