Rewrite wildcard path not working for nested routes

[keslert]

What version of Next.js are you using?

10.1.3

What version of Node.js are you using?

14.16.0

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

Vercel

Describe the Bug

Using the following wildcard path matching doesn't match nested routes.

{
  source: "/@:username*",
  destination: "/u/:username*",
}

This works: /@vercel
This doesn't work: /@vercel/settings

If I change to the following:

{
  source: "/@/:username*",
  destination: "/u/:username*",
}

This works: /@/vercel
This works: /@/vercel/settings

Expected Behavior

The wildcard path matching should work on nested routes.

To Reproduce

// next.config.js
module.exports = {
  future: {
    webpack5: true,
  },
  async rewrites() {
    return [
      {
        source: "/@:username*",
        destination: "/u/:username*",
      },
    ]
  }
}

[kylemarshall18]

@keslert I believe you have to use regex path matching to get the expected behaviour (or as a work around):

async rewrites() {
    return [
      {
        source: '/:username(@.*)',
        destination: '/u/:username',
      },
    ]
  },

This will match /@vercel & /@vercel/settings but not /vercel or /vercel/settings

[ijjk]

Closing as the solution in #24288 (comment) is correct as using :path* with a leading character changes the behavior for non-regex matching.

[balazsorban44]

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.