potential racecondition?

First off, thanks for creating another awesome lib @vkarpov15 😃

I am seeing some sort of racecondition but have troubles spotting it reliably why its happening (or if this has nothing to do with awaitjs/express).

Following is an abstraction of what I am doing. Generally what I want is to have multiple different files, each with a Router from @awaitjs/express that are then put together like the following;

//tags.ts
export const tagsRouter = Router({ mergeParams: true });
tagsRouter.getAsync('/*', async (req, res) => {
	console.log('Tag routes..')
	await new Promise<void>((resolve) => {
		setTimeout(resolve, 5000)
	})
	console.log('Tags finished..')
	next()
})
tagsRouter.getAsync('/*', async (req, res) => {
	const data = await something()
	console.log('Do Tag..')
	res.json(data)
})
// more routes...

//models.ts
export const modelsRouter = Router({ mergeParams: true });
modelsRouter.getAsync('/*', async (req, res) => {
	console.log('Model routes..')
	await new Promise<void>((resolve) => {
		setTimeout(resolve, 5000)
	})
	console.log('Models finished..')
	next()
})
// more routes...

//main.ts
import {tagsRouter} from 'tags'
import {modelsRouter} from 'models'
import {ensureAccess} from '../access';
export const mainRouter = Router({ mergeParams: true });

mainRouter.use(':userId/*', ensureAccess); //some access control which makes a async call to the database
mainRouter.use(':userId/tags', tagsRouter);
mainRouter.use(':userId/models', modelsRouter); 

When running this from time to time I get the outputs in a wrong order

Tag routes..
Do Tag..
Tags Finished..

instead of

Tag routes..
Tags Finished..
Do Tag..

Am I messing something up in my setup? Am I misunderstanding this library?

[7opf]

I’ve also run into this issue and confirm @EvanSmith-git branch fixes it in our tests.

[japrescott]

thanks @vkarpov15 ❤️