vite-plugin-pages VS vitesse-ssr-template

vite-plugin-pages, auto generates routes for Vue components in the src/pages directory.

References to compare with something at all: * https://github.com/samchon/typescript-json (input transformer) * https://github.com/trpc/trpc (state-of-the-art end-to-end api) * https://github.com/spa5k/fastify-file-routes * https://github.com/hannoeru/vite-plugin-pages (frontend file-based routing)

Its more natural fit / easier to use for blog site. https://github.com/hannoeru/vite-plugin-pages is good too

I'm not sure what Nuxt adds. The vite-plugin-pages, has removed the only usecase I had for nuxt.

The good news is that, similar needs have been solved in the vite community with https://github.com/hannoeru/vite-plugin-pages, we just need to port it to webpack and https://github.com/unjs/unplugin got our back.

Thanks! I'll maybe work on some vite plugin to make it work here too since there are plugins like https://github.com/hannoeru/vite-plugin-pages

Since official SolidJS starter template are vite-based we can easily use vite-plugin-pages to create automatic routing a.k.a file based routing with official solid-app-router package.

File-based routing

Vitesse SSR deployed to Vercel puts out Lighthouse scores in the 90s. Practically does already what all Nuxt 3 will supposedly do. I think most component libraries are unnecessary and bloaty. Just roll your own with only what you need.

Nobody gave you a serious reply but Nuxt 2 + Composition API is 90% the same and it'll upgrade somewhat gracefully. If you're dying to use Vue 3 you can get most of the way with Vitesse

There is a vitesse fork for SSR though.

Here's a great template for SSR + Vite: https://github.com/frandiox/vitesse-ssr-template