vitedge
rakkasjs
vitedge | rakkasjs | |
---|---|---|
6 | 15 | |
723 | 1,030 | |
- | 1.0% | |
0.0 | 9.1 | |
3 months ago | 7 days ago | |
JavaScript | 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.
vitedge
-
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,
-
What is the best solution for a server-side rendered Vue 3 application with Cloudflare?
Given this situation, I think there are three solutions for my application: 1. Nuxt 3, which has support for rendering via Cloudflare Workers. 2. Cloudflare Pages, which recently got support for SSR via Workers. 3. Vitedge, which seems like a plugin for the Vite build system that targets Cloudflare Workers.
-
Three Cool Rakkas Features that Next.js Lacks
Note that we're not talking about Cloudflare Pages, which Next.js supports as a static deployment target, but actual server-rendered (well, technically speaking “edge-rendered”) React applications with support for API routes. This is a rare feature among React frameworks (I'm only aware of Flareact and Vitedge).
-
What do you guys prefer to use with Laravel. React, Vue or Blade ;
Vue isn't incompatible with caching, but it admittedly does need a fancier cache that runs workers: https://github.com/frandiox/vitedge is one example of such an edge-optimized thing.
-
Your goto setup for new projects that require SPA functionality
I love Inertia, but it's useless for SSR. They've had an "early access" SSR for ages now, but I don't have faith it'll be ready any day soon. Separate API and UI projects are the way to go, the UI built with something like Vitedge for edge-side rendering.
- Vitedge: SSR at the edge using Vite and Cloudflare Workers
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
What are some alternatives?
cloudflare-worker-router - A super lightweight router (1.0K) with middleware support and ZERO dependencies for Cloudflare Workers.
vike - 🔨 Like Next.js / Nuxt but as do-one-thing-do-it-well Vite plugin.
electron-vite-tailwind-starter - This Starter utilizes Electron, Vite and Tailwindcss in combination. It trys to adhare best practices.
wrangler-legacy - 🤠 Home to Wrangler v1 (deprecated)
cloudflare-worker-router-template - A wrangler template for a super lightweight router (3.6 kB) with middleware support and ZERO dependencies for CloudFlare Workers, inspired by express.js syntax.
rakkas-realworld - Rakkas implementation of the RealWorld demo
petite-vue - 6kb subset of Vue optimized for progressive enhancement
Rollup - Next-generation ES module bundler
Google-Drive-Index - Index Google Drive Files Easily and Free
vite-ssr - Use Vite for server side rendering in Node
adapter-cloudflare-cache - Temporary SvelteKit adapter for Cloudflare Workers to enable caching
vite - Next generation frontend tooling. It's fast!