vike
waku
vike | waku | |
---|---|---|
66 | 9 | |
3,609 | 3,845 | |
3.1% | - | |
10.0 | 9.7 | |
6 days ago | 5 days ago | |
TypeScript | TypeScript | |
MIT License | 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.
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
waku
-
React Server Components Example with Next.js
The moderators at Reactiflux pointed me toward Waku (also developed by Daishi Kato) as a potential alternative. However, Daishi explicitly recommends using the framework on non-production projects.
- Waku – The Minimal React Framework
-
Show HN: A live deployment of Waku RSC's examples
Waku (https://waku.gg/) is a new vite-based RSC framework with an emphasis on simplicity and developer experience. And Waku Land is a website I built to host each example from Waku's source code. It redeploys from Waku's main branch once every six hours.
-
The Current State of React Server Components: A Guide for the Perplexed
The other piece of important information to acknowledge here is that when we say RSCs need a framework, “framework” effectively just means “Next.js.” There are some smaller frameworks (like Waku) that support RSCs. There are also some larger and more established frameworks (like Redwood) that have plans to support RSCs or (like Gatsby) only support RSCs in beta. We will likely see this change once we get React 19 and RSCs are part of the Stable version. However, for now, Next.js is currently the only framework recommended in the official React docs that supports server components.
-
Streams and React Server Components
Many developers have used streams when building technology, but how many have truly understood their intricacies and their connection to React Server Components? Personally, the concept never quite clicked for me. It wasn't until contributing to Waku and being curious about how RSCs stream html—requiring me to take them seriously. Waku is a minimal layer over React Server Components using Vite.
-
Next.js 14
> Next.js is still the only actual implementation of RSC
Here's one https://github.com/dai-shi/waku. Also, Redwood is "all in on Server Components" https://tom.preston-werner.com/2023/05/30/redwoods-next-epoc....
- Waku: The Minimalist React Framework with Server Components
-
Am I the only one that thinks that the direction of React is wrong?
You can. You would just need to put in the work to go look at the (still entirely undocumented) React core library pieces of RSCs, and figure out how to integrate those into your bundler and router of choice. Other devs are already doing that, such as https://github.com/dai-shi/wakuwork
What are some alternatives?
vite-ssr - Use Vite for server side rendering in Node
Next.js - The React Framework
Next-JS-Landing-Page-Starter-Template - 🚀 Free NextJS Landing Page Template written in Tailwind CSS 3 and TypeScript ⚡️ Made with developer experience first: Next.js 14 + TypeScript + ESLint + Prettier + Husky + Lint-Staged + VSCode + Netlify + PostCSS + Tailwind CSS
vite-imagetools - Load and transform images using a toolbox :toolbox: of custom import directives!
hyperwave - 🌊 build rich, performant UIs with the best possible developer experience
ts-node - TypeScript execution and REPL for node.js
Next-JS-Landing-Page-Starter-Templ
vite-plugin-vue2 - Vue2 plugin for Vite
redwood - The App Framework for Startups
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
next-auth - Authentication for the Web.