Support for spread operator in middleware matcher

[SamRoehrich]

Describe the feature you'd like to request

I would like to have support for the spread operator in the middlware matcher so that if I can use an array of paths instead of having to manually type them out.

Consider a use case like:

// middlware.js
const paths = {
    '/profile': {
        func: () => {}
    },
    '/settings': {
        func: () => {}
    }
}

export function middleware(req) {
    const pathname = req.nextUrl.pathname

    if(Object.keys(paths).includes(pathname) return paths[pathname].func()

    return NextResponse.next()
}

export const matcher = [...Object.keys(paths)]

Currently the above example throws this error in the console:
Unsupported spread operator in the Array Expression at "config.matcher".

Describe the solution you'd like

Support for the spread operator in the matcher.

Describe alternatives you've considered

Writing out paths.

[thescientist13]

Yes, this would be great. Trying to transition a lot of old -> new routes for a redesign will be a bit tedious having to list them all out individually 😵

edit: I would add though for redirects, if that is your use case, the redirects feature in next.config.js is working quite well as an alternative approach, just trying it out right now.

[kaloyanBozhkov]

Would be cool to have this, ran into it myself today.

[raflymln]

+1 on this

[YahyaBagia]

+1 on this

[kevinlandsberg]

+1

[leochiu-a]

+1

[acron0]

+1

[PrashantIndurkar]

+1

[albertininm]

+1

[GBvanDam]

Would it maybe even be stronger to enable multiple middlewares in a file-system based nested manner? This way, not only the spread operator is added, but several more things?

#69866 (comment)