Regex path support

[selimdoyranli]

I can't understand why a feature that is so widely used in the real world or that has to be used for SEO would be removed from such a popular library or framework. It feels like a step backwards, and I'm really upset about it. I've been trying to figure out how to implement this feature on my website for about a week now. If I had known that this feature, which is supported by almost all router libraries, would suddenly be removed from here, I wouldn't have chosen it. Of course, I realize that this can be addressed with a single file like catch-slug.tsx or smart-route.tsx, but in my opinion, this only serves to worsen the code and cause bundle size issues by including two route.tsx files in the same file. Removing it might improve the framework's size or speed, but real-world applications often require these features, and a balance needs to be struck. Sacrificing one aspect for the other never felt like the right solution to me. Unfortunately, I've started leaning toward alternatives like tanstack, no matter how long the refactoring process takes. I hope you take everyone's feedback into consideration. Regards.

an example issue

http://localhost:4200/technology -> category.tsx http://localhost:4200/technology/mobile -> category.tsx (conflict with news-detail) http://localhost:4200/technology/mobile/news-123 -> news-detail.tsx http://localhost:4200/technology/news-123 -> news-detail.tsx (conflict with category) 

route('/:category/:subCategory?/:slug-:id', './routes/news-detail.tsx'), route('/:category/:subCategory?', './routes/category.tsx') 

it doesn't work , i got conflicts

related with #8254 #6808 #9278 #10720