vitesse-ssr-template
test-nuxt
| vitesse-ssr-template | test-nuxt | |
|---|---|---|
| 6 | 2 | |
| 187 | 0 | |
| - | - | |
| 0.0 | 3.8 | |
| over 2 years ago | about 2 years ago | |
| TypeScript | Vue | |
| MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vitesse-ssr-template
- Reasons to not use nuxt?
-
Need input/advice : are good CWVs even possible with Nuxt + Vuetify ?
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.
-
Is Nuxt 3 ready for production? Is anyone using it?
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
-
Vue 3 SSR
There is a vitesse fork for SSR though.
-
[PAID] Need help with setting up my vue 3 ssr project (without using Nuxt)
Here's a great template for SSR + Vite: https://github.com/frandiox/vitesse-ssr-template
- Vitesse SSR starter template deploying to Vercel
test-nuxt
-
Need input/advice : are good CWVs even possible with Nuxt + Vuetify ?
My company's website is currently built in GatsbyJS. I love Vue and I want to make a case for switching to it, as we're currently rebranding. Our designer has started delivering mockups, based on Material UI. That being the case, I wanted to try Nuxt + Vuetify. Unfortunately, I'm having a really hard time with performance, especially with Lighthouse. Vuetify looks bloated : my barebones install scores at 80 on mobile, and even after enabling treeshaking and following all the docs, the highest score I can get on mobile is ~75 for an almost empty page (see page here, performance report here, and repo here) and I don't know what else I can optimize. And as soon as I make a "mistake" like not 100% optimizing an image, it drops to the 40-60 range. I just cannot justify using this framework if I can't at least achieve a low green score in CWVs, the team simply won't buy into it.
-
Need help : Custom breakpoints not working with Vuetify
Repo : https://github.com/lekevoid/test-nuxt
What are some alternatives?
vike - 🔨 Like Next.js / Nuxt but as do-one-thing-do-it-well Vite plugin.
vite-ssg - Static site generation for Vue 3 on Vite
unplugin-vue-components - 📲 On-demand components auto importing for Vue
vue3-example-ssr - Server Sider Rendering (SSR) in Vue 3 - Example App
vite-ssr - Use Vite for server side rendering in Node
vitesse - 🏕 Opinionated Vite + Vue Starter Template
vite-plugin-pages - File system based route generator for ⚡️Vite
nuxt-auth - 🔐 Nuxt user authentication and sessions via authjs (next-auth), local and refresh providers. nuxt-auth wraps NextAuth.js to offer the reliability & convenience of a 12k star library to the nuxt 3 ecosystem with a native developer experience (DX)
prerender - Node server that uses Headless Chrome to render a javascript-rendered page as HTML. To be used in conjunction with prerender middleware.
vite-plugin-md - Markdown with Vue for Vite
vue-ssr - Minimalistic wrapper to develop and run SSR Vue apps 🔗