TypeError: Can not repeat "slug" without a prefix and suffix after 15.5 upgrade

[essuraj]

Summary

Running my code under 15.4.x works fine but when i upgrade i get and error
[TypeError: Can not repeat "slug" without a prefix and suffix]

and the app stops. no issue source, no file info, nothing. not sure what to do

Additional information

No response

Example

No response

[essuraj]

[kishxrx]

Rename one of the dynamic segments so they’re unique, or switch to a catch-all parameter!

app/[category]/[slug]/page.tsx // distinct names

or

app/[...slug]/page.tsx // rest parameter

[essuraj]

all are unique

[icyJoseph]

Mmm second time I am seeing this error today -

Is there any repository I could take a look at? That error is coming all the way from within a path-to-regexp resolve gone wrong, but what exactly 🤔

[essuraj]

not really, this worked fine till 15.4.x since v13. Just breaking in this 15.5 update, i have [...slug] as well as [slug2] both without any duplicate names

[essuraj]

its not even pointing to where the error might be, just immediate crash

[icyJoseph]

Yeah, this is indeed super weird - is it possible to share a tree structure of your file tree?

[essuraj]

[Jonas-PFX]

Im also getting this.
15.4.x works fine, 15.5.0 gives [TypeError: Can not repeat "path" without a prefix and suffix].

[icyJoseph]

In short, this is because path-to-regexp 6.3.0 strengthened their parsing, so whereas this worked before:

      source: "/foo-:slug*",

Now you have to limit what slug is allowed to be:

• /:foo-:slug(\\w+)
• /:foo-:slug([^/]+(?:-[^/]+)*) (not sure about this one, try it out)
• /:foo-:slug([A-Za-z0-9]+) more familiar and easy to read

The regex modifications may vary for your use case.

[mparisot-antescofo]

that did the trick, thanks a lot 🙏

[JasonA-work]

Thank you man! Thanks to you I was able to fix this :)

It seems the only thing that made it crash was:

/foo:slug*

If there was a slash before :slug* like so:

/foo/:slug*

Things will still work just fine.

[gmarriott-brighthr]

Is there an easy way to find the route causing the type error, just as our Next project is quite large with multiple dynamic routes, so it's hard to pinpoint which is causing the issue. Did you search for something in particular to find the route causing concern?

[icyJoseph]

The error message made by path-to-regexp, picks the "name" of the parameter name - so in this case, searching for slug does the trick. Other than that, nope, not right now.