vike
supabase
vike | supabase | |
---|---|---|
66 | 769 | |
3,609 | 66,465 | |
3.1% | 2.9% | |
10.0 | 10.0 | |
6 days ago | 2 days ago | |
TypeScript | TypeScript | |
MIT License | Apache License 2.0 |
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
supabase
-
Wasp x Supabase: Smokin’ Hot Full-Stack Combo 🌶️ 🔥
It was a great experience using Supabase’s rock-solid PostgreSQL database for this app. The DX around that product is phenomenal: viewing and managing the DB data was a lifesaver when you don’t want to craft your own admin panel from scratch.
-
How I migrated from Firebase to Supabase
I didn't really give much thought as to which backend I would use. I already had 2 projects in Supabase (BOXCUT & MineWork), but also a few projects in Firebase too. I was more concerned at the time at actually building the product.
-
How to get free Postgres
Sign up for SupaBase: Head over to SupaBase and sign up. Create a new workspace and project with your preferred names.
-
Creating a Pokémon guessing game using Supabase, Drizzle, and Next.js in just 2 hours!
Setting up Supabase Create a new Supabase project, and get the connection string for the database from settings > database.
-
How To Make An Insanely Fast AI App (Supabase, LLAMA 3 and Groq)
Supabase (start for free)
-
Building a self-creating website with Supabase and AI
Built with Supabase, Astro, Unreal Speech, Stable Diffusion, Replicate, Metropolitan Museum of Art
-
How I built a Markdown Rendered Blog using Supabase and Chakra UI
Supabase will be used for storing article data in the database and the cover image of the article in storage. Chakra UI will be used to provide style to the elements. By using both, we can build the blog with ease.
-
I got #1 Product of the Day on Product Hunt without Spending a Dollar
For AutoRepurpose, I opted for Supabase as the backbone of the backend. It has reliably supported Penelope AI, which garnered over 15k users in 2022 without any issues.
-
AI Inference now available in Supabase Edge Functions
Semantic search demo
-
Creating an OG image using React and Netlify Edge Functions
1. Create a new Supabase project: Visit Supabase and create a new project.
What are some alternatives?
vite-ssr - Use Vite for server side rendering in Node
Appwrite - Your backend, minus the hassle.
Next.js - The React Framework
pocketbase - Open Source realtime backend in 1 file
vite-imagetools - Load and transform images using a toolbox :toolbox: of custom import directives!
nhost - The Open Source Firebase Alternative with GraphQL.
ts-node - TypeScript execution and REPL for node.js
neon - Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, branching, and bottomless storage.
vite-plugin-vue2 - Vue2 plugin for Vite
next-auth - Authentication for the Web.
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
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.