vue-svelte-size-analysis
vike
vue-svelte-size-analysis | vike | |
---|---|---|
18 | 66 | |
300 | 3,588 | |
- | 2.5% | |
0.0 | 10.0 | |
over 1 year ago | 7 days ago | |
JavaScript | TypeScript | |
- | 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.
vue-svelte-size-analysis
- What things sveltekit offer better than other javascript frameworks?
- The State of JS 2022
-
A React Developer's First Take on Solid
but that's not true. see https://krausest.github.io/js-framework-benchmark/current.html. There is also a break-even point in bundle size where svelte gets larger compared to vue. see https://github.com/yyx990803/vue-svelte-size-analysis
-
What's next on your JavaScript framework radar for 2023? (Front End)
i did not ignore it. You can read about it here. There is break-even point where svelte falls off compared to vue as the application grows.
- Anyone know what these recent massive spikes in svelte & vue usage are from?
-
The new wave of React state management
The first version of React was released on 2013, it took almost 10 years for Suspense to exist (we _just_ got it now with React 18), that's what I'm talking about. Even functional components and hooks took a lot of time from them get and implement the idea after they tried to use ES classes and made everything much harder to manage. Context also isn't perfect, I like it but the redraw performance is not amazing and doesn't scale at all to bigger applications.
> https://github.com/yyx990803/vue-svelte-size-analysis
This is an interesting comparison I haven't seen before, I wonder if it's true for a complete application using some lib for state management, routing, etc. and if this isn't just a kind of cherry picked example. Thanks for showing this though.
-
All you need to know about the state of Vue.js in 2022
probably only true for small projects
- Solid.js feels like what I always wanted React to be
-
Memoirs of a lone JavaScript developer PART 2 : Svelte. An awful implementation of an old idea.
You are citing this: https://github.com/yyx990803/vue-svelte-size-analysis
-
JavaScript Framework TodoMVC Size Comparison
There isn't only the size of the runtime but the size of the component code. Not all components are equal. Templates in each framework compile differently. Evan You, creator of Vue put together a comparison between Svelte and Vue which was pretty illuminating.
vike
-
SSRx vs. Vinxi vs. Vike - for SSR with Vite
Here are some collected notes of the distinctions between SSRx, Vinxi and Vike, to share with anyone else searching the web. Since my Google search came up empty, and I had to ask around on Twitter/X and GitHub to find out.
- Vike – Meta Framework Alternative
-
Triplit: Open-source DB that syncs data between server and browser in real-time
We're working on exactly this. You can already do this with Triplit but it's challenging to make an out of the box solution because each framework passes context/data different from server to client differently. There's a cool project called [Vike](https://github.com/vikejs/vike) that generalizes this pattern across SSR'd UI frameworks
-
Can't stand Next JS-- alternatives w/ Vite?
Anyone have experience with https://github.com/vikejs/vike?
-
Waku: The Minimalist React Framework with Server Components
have you seen https://vite-plugin-ssr.com/ ? i've only browsed their docs, but AFAICT their pitch that it's a more DIY approach to a framework, where you keep a lot of control over how things are wired together.
-
The theory versus the practice of “static websites”
I agree and, as the author of vite-plugin-ssr[1], that's what I recommend to my users: go for static whenever you can.
I think it's something every web developer should be aware of. Static is indeed a lot simpler than dynamic.
I've wrote more about it over here[2] (SSG = static, SSR = dynamic).
[1]: https://vite-plugin-ssr.com
-
What's the best ISR (and SSR) React frameworks? (looking for NextJS alternative)
Maybe vite-plugin-ssr? It's pretty unopinionated and doesn't get in your way.
-
Next.js App Router Update
Also have a look at https://vite-plugin-ssr.com/ (author here).
VPS is slightly lower level which gives you a lot more control: integrate with your existing Node.js backend (use any backend framework you want), deploy anywhere, use any React alternative (Solid, Preact, ...) and any data fetching tool (e.g. Relay can't really be used with Next.js).
The flip side is that you've to write a little bit more glue code. Although this will be alleviated by a lot with projects such as Bati[0], Stem[1], and vike-react (see Vike Rebranding[2]).
VPS also cares a ton about details, such as hooks for full control over i18n (use any i18n strategy you want), better Base URL support (VPS supports setting a different base for your server and your CDN), automatic deploy synchronisation, domain-driven file structure, polished and helpful error messages (especially the next upcoming release), ...
Detailed comparison with Next.js: [3].
If you run into any blocker then it's quickly fixed (or at least a workaround is proposed).
It supports not only SSR and pre-rendering, but also SPA in case you don't need SSR. It's going to support RSC but doesn't yet (RSC isn't ready for production).
Because it's lower level and because it's decoupled from React everything is designed in an agnostic way and with meticulous care. In other words: vite-plugin-ssr is becoming a robust foundation. There are breaking changes coming for the v1 release but beyond that chances are that there won't be any breaking change for years in a row.
In a nutshell: vite-plugin-ssr takes care of the frontend and only the frontend. You keep control over your architecture. (Whereas frameworks tend to put themselves right in the middle of your architecture restricting you in fundemetanl ways.)
Last but not least: it's powered by Vite which means blazing fast HMR.
[0] https://batijs.github.io
[1] https://stemjs.com/
[2] https://github.com/brillout/vite-plugin-ssr/issues/736
[3] https://vite-plugin-ssr.com/nextjs-comparison
-
React Server Side Rendering(SSR)
Now by default, Vite doesn't do SSR. One way to do Vite+SSR is to use vite-plugin-ssr. You can scaffold an example project that does SSR based on some dynamic data:
-
NextJS app router is complete failure, what alternatives do you recommend for react SSR and ISR?
vite-plugin-ssr
What are some alternatives?
pinia - 🍍 Intuitive, type safe, light and flexible Store for Vue using the composition api with DevTools support
vite-ssr - Use Vite for server side rendering in Node
realworld - SvelteKit implementation of the RealWorld app
Next.js - The React Framework
vue-native-core - Vue Native is a framework to build cross platform native mobile apps using JavaScript
vite-imagetools - Load and transform images using a toolbox :toolbox: of custom import directives!
devtools - Replay.io DevTools
ts-node - TypeScript execution and REPL for node.js
qwik - Instant-loading web apps, without effort
vite-plugin-vue2 - Vue2 plugin for Vite
inertia - Inertia.js lets you quickly build modern single-page React, Vue and Svelte apps using classic server-side routing and controllers.
nextjs-tailwind-ionic-capacitor-starter - A starting point for building an iOS, Android, and Progressive Web App with Tailwind CSS, React w/ Next.js, Ionic Framework, and Capacitor