handle .page.vue extension

[stefanprobst]

when configuring the vite plugin with a .page.vue extension, the generated route config includes e.g. /index.page for ./src/pages/index.page.vue:

// vite.config.ts
import vue from '@vitejs/plugin-vue'
import router from 'unplugin-vue-router/vite'
import { defineConfig } from 'vite'

export default defineConfig({
  plugins: [
    router({ dts: './routes.d.ts', extensions: ['.page.vue'] }),
    vue(),
  ],
})

// snippet from generated routes.d.ts
declare module 'vue-router/auto/routes' {
  export interface RouteNamedMap {
    '/index.page': RouteRecordInfo<
      '/index.page',
      '/index/page',
      Record<never, never>,
      Record<never, never>
    >
  }
}

[posva]

The . Here has a special meaning and is transformed to a slash

what are you expecting exactly?

[stefanprobst]

when i configure a file extension which includes a dot, e.g. extensions: ["page.vue"], i would expect that this dot will be treated as being part of the file extension and not converted to a slash.

i guess this would mean that trimExtension should not simply slice off everything after the last dot, but use the actual configured extensions.

[posva]

I see. What is the idea of having .page.vue exactly? Is it more of a domain-based file organization, something similar to Next.js and SvelteKit conventions?

[stefanprobst]

Is it more of a domain-based file organization, something similar to Next.js and SvelteKit conventions?

yep, exactly.