Export page utility functions

[BobbieGoede]

Describe the feature

• Related Segment parser implementation syncing nuxt-modules/i18n#2411
• Blocks feat: custom routes named config nuxt-modules/i18n#2408

In @nuxtjs/i18n (v8) we manually sync the implementation of parseSegment and getRoutePath as these are not exported. Not sure if exporting as is, or in @nuxt/kit, or elsewhere would make more sense.

Additional information

• Would you be willing to help implement this feature?
• Could this feature be implemented as a module?

Final checks

• Read the contribution guide.
• Check existing discussions and issues.

[danielroe]

We think it would be good to create a single library we can depend on in Nuxt and in i18n.

If @posva would like to expose it we could depend on it, otherwise I am happy to create a library.

[posva]

Do you mean the matcher? Or do you have some specific functions in mind? There is already an exposed createMatcher(). It's marked as internal of course as it's not intended for broader usage but it's fine if well-known parts of the ecosystem like Nuxt and i18n use it. A few years ago I started a project to open source the underlying layers of the route parsing but I never made it public 😅

[danielroe]

I'm meaning a library to convert/parse file system paths into route matching syntax.

[BobbieGoede]

There is already an exposed createMatcher(). It's marked as internal of course as it's not intended for broader usage but it's fine if well-known parts of the ecosystem like Nuxt and i18n use it.

I have been holding off on using this for i18n routing since it was marked internal 😅 .. I'll look into using it.

A few years ago I started a project to open source the underlying layers of the route parsing but I never made it public 😅

I would be interested in this, for i18n routing I keep on wanting to use Vue Router internal utilities like parseURL, parseQuery as well as their stringifying couterparts. We want to match the behaviour of Vue Router, as we internally parse paths and change it a bit to resolve a localized route, especially encoding/decoding paths has been difficult to match, but maybe createRouterMatcher is intended for such use cases.

I'm meaning a library to convert/parse file system paths into route matching syntax.

This would be useful for Nuxt i18n (and other file based i18n routing as well nuxt-modules/i18n#2686 (comment) /cc @kazupon), I don't think https://github.com/posva/unplugin-vue-router exposes this right?

[harlan-zw]

I have also found myself copying these functions in some modules so quite interested in this.