reactfire
rowy
Our great sponsors
reactfire | rowy | |
---|---|---|
17 | 20 | |
3,471 | 5,615 | |
0.7% | 2.3% | |
5.1 | 8.5 | |
about 11 hours ago | 8 days ago | |
TypeScript | TypeScript | |
MIT License | GNU General Public License v3.0 or later |
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.
reactfire
-
Angular Fire equivalent for React?
ReactFire
-
Can't call Google Cloud Function from a react app. I get googleauth.js:17 Uncaught Error: Cannot find module 'child_process' in my browser's console
Are you using Firebase? If not, you probably should. You can call functions (with Auth) from your react app. There's a framework you can use to help: https://github.com/FirebaseExtended/reactfire
-
Convex vs. Firebase
I was an early developer at Firebase. I think we made Firebase so easy to use and never spoke on about the technicals that the whole software ecosystem now underestimates the complexity involved. I see various Firebase competitors asserting various "mistakes it makes" without really understanding what it delivers, which is understandable because we never marketed it like that because we spoke only about how it can help you build easier.
The idea that n queries instead of a join is slow is not as true as you would think. Firestore supports streaming and pipelines at its core, and can reuse cache across operations. At the end of the day, the data goes over a narrow network channel. If you can saturate the channel, and don't leave any gaps, what's the performance difference if the data comes from a single query or many that are back-to-back. The data is transferred to the client either way. Both Firebase databases are pipelined, so this "many round trip" argument is not a decent argument if the client can issue the queries without waiting for responses (such as the code in this article).
The other is consistency levels and correctness. I constantly see devs call Firebase an eventually consistent database which is wrong, its causally consistent [1], and this makes a huge difference when trying to do OLTP. The offline capabilities are built on the consistency primitives, and it's the only way it can work. So while this convex article is banging on about "End-to-End Correctness Philosophy", they miss the most important quality of correctness, and if they are not careful, will miss the required engineering, and then be unable to deliver an offline cache over real-time streams. I see this playing out with Supabase, I warned them personally before they got into YCombinator that what they were building was not causally consistent. Since then, they have had to rearchitect their real-time features after shipping them. (I have not reviewed their latest design yet so I have no idea whether they have it right yet).
Many things sucked about Firebase. The bespoke security rules and the lack of views. So Convex is on the money shipping functions on the backend. I think Supabase is shipping competitors' mistakes with row-level security language. Personally, I think Firebase's mistakes can be fixed with the addition of an open-source Firebase server [1], as the clients are already open source and the mistakes are all to do with just the server. The real tech was always in the clients anyway (offline cache, connection management, operation queues).
It will be interesting to see if building expressly for React is a good idea. Firebase shipped many adapters, like https://github.com/FirebaseExtended/reactfire, using the "thin-waist" principle of not over-fitting. But Javascript technology moved from callbacks to async while Firebase was in the field, so the current API is not now idiomatic. But convex is setting itself for even more ecosystem fragility, what if React changes API or falls out of favor? This is a big risk! I hope they can roll with whatever happens!
-
Do you have to use an ODM for firestore?
Since you mentioned you're also using React, we have a React specific library (ReactFire) that also helps out quite a bit.
-
Intro To ReactFire v4 - Login, Logout Create Account And Protected Routes
From the ReactFire Example Code, see this is in AppAuthWrapper.tsx. The AuthWrapper code is from the reactfire repo to account for the removal of AuthCheck component
This is a quick walkthrough of a code example using ReactFire v4 in an application. The application supports login, logout, create an account, and protected routes. We also walk through two approaches for protecting routes since the AuthCheck component that existed in v3 no longer exists in v4 of ReactFire.
-
React Query + Firestore = ❤️
reactfire
- Usando Firebase para autenticar en Django REST Framework
-
Has anyone had any success in setting up React tests using Create React App + Jest + Jsdom + Firebase Emulators
Maybe someone over on the ReactFire repo can give some advice:https://github.com/FirebaseExtended/reactfire
-
How To Use ReactFire & Redux Using Firebase Emulator to Build a CRUD Application
ReactFire - GitHub Project ReactFire Overview - Documentation Firebase Emulator - Overview
rowy
-
AI Grant Traction in OSS Startups
View on GitHub
-
Open Source alternatives to tools you Pay for
Rowy - Open Source Alternative to Airtable
-
A modern, open-source spreadsheet that goes beyond the grid
You can checkout opensource project Rowyhttps://github.com/rowyio/rowy - it a spreadsheet UI for database and can do databasy things like you said!
formulas but in JS/TS,
-
how do you move to second page in firestone?
Just thought will put it out here as it seems like a pain point we also faced when trying to use Firestore console UI...trying to manage the data/find it etc was a pain :( So we built an open-source spreadsheet-like UI to manage your Firestore data as easily. Hope you find it useful :) Website: https://rowy.io/ Github: https://github.com/rowyio/rowy
-
Firebase CMS
Github: https://github.com/rowyio/rowy
Website: https://rowy.io
-
I made an Open-source FireStore UI tool to make development with Firestore less painful!
Also from the same makers, there is rowy.io however that is completely different beast in its own :)
-
Rowy: Open-source Airtable alternative on Google Cloud
Tables I would image when it is released, should be a great Airtable alternative. With Rowy, we are building an Airtable like experience but your actual database on Firestore. So that developers can continue to build their apps. https://github.com/rowyio/rowy
What scale have you tested the UI at? Do you have any demo / benchmarks for over 1M rows?
Reading through the infinite scrolling PR [1] it looks like scrolling isn’t virtualized (like Airtable’s) so the browser will start choking when it has too many elements in the DOM.
What are some alternatives?
nocodb - 🔥 🔥 🔥 Open Source Airtable Alternative
react-query-firebase - React Query hooks for managing asynchronous operations with Firebase. Supports Authentication, Analytics, Firestore & Realtime Database.
IdleonCompanion - Everything you'll ever need for Legends of Idleon!
use-pagination-firestore - 🔥 React hook for non-cumulative pagination of Firebase Firestore collections
obsidian-db-folder - Obsidian Plugin to Allow Notion like database based on folders
strapi-connector-firestore - Strapi database connector for Firestore database on Google Cloud Platform.
Directus - The Modern Data Stack 🐰 — Directus is an instant REST+GraphQL API and intuitive no-code data collaboration app for any SQL database.
refi-app - A tool to make interacting with Firestore less painful
Hasura - Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.
react-famous - React bridge to Famo.us
Redux Slim Async - :alien: A Redux middleware to ease the pain of tracking the status of an async action
React Data Grid - Feature-rich and customizable data grid React component