feat: support passing options to `TypedRouterOptions` when using `experimental.typedPages`

[danielwaltz]

feat: support passing options to `TypedRouterOptions` when using `experimental.typedPages`

[manniL]

Can you provide a reproduction where/when route names collide? Does that also happen without typedPages?

Unfortunately, functions are not allowed at all in the nuxt.config.ts to make sure the config is serializable but probably another way (like router.options.ts) would be an option for configuration

[github-actions]

Would you be able to provide a reproduction? 🙏

More info

Why do I need to provide a reproduction?

Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making.

What will happen?

If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritize it based on its severity and how many people we think it might affect.

If needs reproduction labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it.

How can I create a reproduction?

We have a couple of templates for starting with a minimal reproduction:

👉 https://stackblitz.com/github/nuxt/starter/tree/v3-stackblitz
👉 https://codesandbox.io/s/github/nuxt/starter/v3-codesandbox

A public GitHub repository is also perfect. 👌

Please ensure that the reproduction is as minimal as possible. See more details in our guide.

You might also find these other articles interesting and/or helpful:

• The Importance of Reproductions
• How to Generate a Minimal, Complete, and Verifiable Example

[danielwaltz]

@manniL Absolutely! Here's a minimal as I could make it reproduction of the issue.

https://stackblitz.com/edit/nuxt-starter-1zwqrx?file=nuxt.config.ts

For context, I created logical route groups for /account/admin and /account/user, where the goal is to not have the paths /admin and /user appear in the url, instead having their child pages show directly under /account. You can see this working without any changes in the example.

To reproduce the issue with typedPages, enable the option and open the utils/directory.ts file and swap the commented blocks of code. You should see type errors in the directory map, and if you inspect the keys on the RouteNamedMap type from vue-router/auto/routes you'll see that some pages are missing (presumably because they are using the same path).

This is why I think it would be useful to provide custom logic to generate the name, so I can use more info than just the path to define what is a unique route.

I get this is kind of a unique case born from a desire for logical grouping of routes, but I do still think it could be useful to provide custom config for other use cases (and this could help support creating a nuxt module that enables support for logical page groups which I have WIP code for).