rakkasjs
vike
rakkasjs | vike | |
---|---|---|
15 | 66 | |
1,032 | 3,630 | |
1.2% | 3.7% | |
9.1 | 10.0 | |
6 days ago | about 3 hours 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.
rakkasjs
-
Creating a Twitter clone for Cloudflare Workers with Rakkas: Part 1
This article is a walk-through of creating a Twitter clone with Rakkas, a bleeding-edge React framework powered by Vite. Our Twitter clone, which we'll call ublog, is going to:
- Show HN: Vite-Powered React Framework
-
Rakkas 0.6: Bleeding edge React framework
Rakkas uses experimental and/or beta features of React and Vite. As such, expect breaking changes until we hit 1.0. But go ahead and give it a try and share your thoughts. Star us on Github, join our Discord server, and follow me on Twitter for updates.
-
Rakkas 0.6: Bleeding-edge React framework
💃 Rakkas, the bleeding edge React framework powered by Vite, has just released version 0.6.0. First release since December, this is the largest and least backward compatible update so far. But we believe the quantity and the quality of the new features justify the number of breaking changes. See if you agree.
-
useServerSideQuery: like getServerSideProps but on steroids
I wanted to share a rough demo of an upcoming Rakkas feature that I'm really excited about: Behold useServerSideQuery :)
-
Vite + Vite Plugin SSR vs NextJS
Today, Nextjs is not only cool guy in the town, A lot of meta frameworks exist like Astro, Remix. There are a few ssr frameworks also build over Vite - such as - https://vitedge.js.org/, https://rakkasjs.org/, https://github.com/frandiox/vite-ssr,
-
Getting Started: Gatsby vs. Next.js vs. Remix
I, for one, enjoy doing this (I even built my own framework from scratch. But most people don't want to make a shovel first so they can dig. They just want to dig. If you have a hand made shovel that works for you, good for you. Most people don't have one and don't want to spend time and energy on building one. That's reasonable.
-
Creating json/cache files during "Build/Deploy" time to save on the cost of the api/time calls?
Cool. Svelte Kit can prerender API routes which solves the same problem. Shameless self-promo follows: I copied it for Rakkas, a Vite-powered React framework similar to Next.js. You may want to check it out.
-
Three Cool Rakkas Features that Next.js Lacks
We all know Next.js is awesome. But Rakkas does put a few unique features on the table. It's still young and not yet ready for production use but go ahead and give it a try and share your thoughts. Star us on Github and talk about Rakkas if you like what you see. If you have any questions, problems, or suggestions open a Github issue. If you want to contribute, fork and send a pull request. Check out the open issues to see how you can help. All feedback is welcome, positive or negative.
Thanks, cool feature I didn't know about. Opened an issue: https://github.com/rakkasjs/rakkasjs/issues/27
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?
wrangler-legacy - 🤠 Home to Wrangler v1 (deprecated)
vite-ssr - Use Vite for server side rendering in Node
rakkas-realworld - Rakkas implementation of the RealWorld demo
Next.js - The React Framework
Rollup - Next-generation ES module bundler
vite-imagetools - Load and transform images using a toolbox :toolbox: of custom import directives!
ts-node - TypeScript execution and REPL for node.js
vite - Next generation frontend tooling. It's fast!
vite-plugin-vue2 - Vue2 plugin for Vite
realworld - "The mother of all demo apps" — Exemplary fullstack Medium.com clone powered by React, Angular, Node, Django, and many more
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