Ross Bratton

I understand why you might want to stick to Jest, but I'd like to put forward a suggestion of using [Vitest](https://vitest.dev). It has a Jest-like API, TypeScript support out-of-the-box, and...

Hey @d0whc3r, thanks for your interest! Yes, I think adding layouts as a feature is a good idea 😄 A solution similar to Routify's seems like a sensible choice, I'm...

Layouts are in a sense already a feature, as you can create a layout for a subset of pages by using the nested routes feature like so: ``` pages/ users.vue

I think I prefer to have the layout file named something like `{layout}.vue` rather than `_layout.vue` as it would be closer to the syntax for dynamic routes. Also perhaps the...

Hey @Septias, great question. This isn't currently supported, but I plan to add support soon via a custom Vue SFC block where you'd be able to set route config. For...

Hi, whilst I'm working on adding that custom SFC block, I thought that it was worth noting that as of release v0.5 you can now supply an [`extendRoute` function](https://github.com/brattonross/vite-plugin-voie#extendroute) in...

Funny you should say that, I was considering something similar recently. If I'm understanding your suggestion correctly, we could alter the virtual file returned by the plugin so that instead...

Hey @delaneyj, I'm not sure that I'm following, but hopefully I can try to make things clearer for you. Let's say you have the following folder structure: ``` pages/ dashboard/...

I'm also interested in being able to share config, but also sharing config in a more modular way e.g. through the use of plugins. The particular use case that I'm...

I appreciate that it is possibly more complex than it is worth to implement. The first thing that comes to mind is: ```yml ls: .js: snake_case .ts: snake_case | camelCase...