Is there any way to access the configs of all routes?

[iamchanii]

I want to utilize the meta feature to manage the UI data needed to display the sidebar declaratively and close to the route file.

export default {
  meta: {
    menu: {
      env: {
        server: true,
        client: true,
      },
      cumulative: true,
    },
  },
}

I see that I can use pageContext.configEntries or pageContext.sources, but if it is not the active path, the menu configuration of the associated path does not appear to be available.

/pages/page-a/
/pages/page-a/page-a-1
/pages/page-b

When a route is configured as shown above, page-a-1 cannot see the configuration for page-b. This feels natural. However, I would like to access the configuration of the entire route from a component like +Layout.

Is there a way to do this or is it possible to implement a feature?

[iamchanii]

Self answered: Use eager property

[iamchanii]

For anyone who wants to utilize the meta feature, eager will be an attractive feature. I was able to find something related in the markdown documentation: https://vike.dev/markdown#with-a-custom-setting-eager

[brillout]

Automatically generating the links of a sidebar is most useful for SSG markdown apps — e.g. Vike's docs has hundreds of pages.

I wonder in what context you need this if it isn't for a markdown app?

[iamchanii]

I want to utilize the meta feature to manage the UI data needed to display the sidebar declaratively and close to the route file.

I am developing an admin application (not SSG) using Vike. I think it's a great feature to have even if we're not building markdown apps.

[brillout]

I agree: it's nice to keep things DRY.

(So far I don't think it's worth it to document it outside of vike.dev/markdown because it's a non-trivial technique. The DRY benefits aren't that important if the number of links in the navigation isn't that high.)