feat(kit): add `prepend` option to `addRouteMiddleware`

[trandaison]

feat(kit): add `prepend` option to `addRouteMiddleware`

[atinux]

Code is here:

nuxt/packages/kit/src/pages.ts

Lines 40 to 59 in 83f8617

	export function addRouteMiddleware (input: NuxtMiddleware | NuxtMiddleware[], options: AddRouteMiddlewareOptions = {}) {
	const nuxt = useNuxt()
	const middlewares = toArray(input)
	nuxt.hook('app:resolve', (app) => {
	for (const middleware of middlewares) {
	const find = app.middleware.findIndex(item => item.name === middleware.name)
	if (find >= 0) {
	const foundPath = app.middleware[find]!.path
	if (foundPath === middleware.path) { continue }
	if (options.override === true) {
	app.middleware[find] = { ...middleware }
	} else {
	logger.warn(`'${middleware.name}' middleware already exists at '${foundPath}'. You can set \`override: true\` to replace it.`)
	}
	} else {
	app.middleware.push({ ...middleware })
	}
	}
	})
	}

If suggest the prepend option to unshift():

Suggestion:

// push() the middleware instead of unshift()
addRouteMiddleware({
      name: 'auth',
      path: resolver.resolve('runtime/auth.ts'),
      global: true
}, { prepend: true })

PR welcome ❤️

[danielroe]

We think it would be a good idea to allow passing an option to addRouteMiddleware (as with addPlugin) to allow adding middleware to the beginning of the middleware array rather than the end.

In general I'd advise against strict middleware ordering dependencies.

[trandaison]

thanks! @atinux, @danielroe

I created a PR for this, please take a look https://github.com/nuxt/nuxt/pull/28496/files