HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
marknutter
firebase-resource
JavaScript2013–2013
marknutter / firebase-resource

firebase-resource

Angular wrapper for Firebase in the style of ng-resource and active-record

2Distinct people
2Mentions
0Explicit recommenders
85GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Angular wrapper for Firebase in the style of ng-resource and active-record

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by day2 dated mentions

Observed mentions: 2013-08-30 17:24:26 UTC to 2013-09-18 19:20:44 UTC.

012013-08-30 00:00:00 UTC to 2013-08-31 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 302013-08-31 00:00:00 UTC to 2013-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-01 00:00:00 UTC to 2013-09-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-02 00:00:00 UTC to 2013-09-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-03 00:00:00 UTC to 2013-09-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-04 00:00:00 UTC to 2013-09-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-05 00:00:00 UTC to 2013-09-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-06 00:00:00 UTC to 2013-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-07 00:00:00 UTC to 2013-09-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-08 00:00:00 UTC to 2013-09-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsSep 82013-09-09 00:00:00 UTC to 2013-09-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-10 00:00:00 UTC to 2013-09-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-11 00:00:00 UTC to 2013-09-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-12 00:00:00 UTC to 2013-09-13 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-13 00:00:00 UTC to 2013-09-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-14 00:00:00 UTC to 2013-09-15 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-15 00:00:00 UTC to 2013-09-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-16 00:00:00 UTC to 2013-09-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-17 00:00:00 UTC to 2013-09-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2013-09-18 00:00:00 UTC to 2013-09-19 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsSep 18

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Aug 302013-08-30 00:00:00 UTC2013-08-31 00:00:00 UTC101
Aug 312013-08-31 00:00:00 UTC2013-09-01 00:00:00 UTC000
Sep 12013-09-01 00:00:00 UTC2013-09-02 00:00:00 UTC000
Sep 22013-09-02 00:00:00 UTC2013-09-03 00:00:00 UTC000
Sep 32013-09-03 00:00:00 UTC2013-09-04 00:00:00 UTC000
Sep 42013-09-04 00:00:00 UTC2013-09-05 00:00:00 UTC000
Sep 52013-09-05 00:00:00 UTC2013-09-06 00:00:00 UTC000
Sep 62013-09-06 00:00:00 UTC2013-09-07 00:00:00 UTC000
Sep 72013-09-07 00:00:00 UTC2013-09-08 00:00:00 UTC000
Sep 82013-09-08 00:00:00 UTC2013-09-09 00:00:00 UTC000
Sep 92013-09-09 00:00:00 UTC2013-09-10 00:00:00 UTC000
Sep 102013-09-10 00:00:00 UTC2013-09-11 00:00:00 UTC000
Sep 112013-09-11 00:00:00 UTC2013-09-12 00:00:00 UTC000
Sep 122013-09-12 00:00:00 UTC2013-09-13 00:00:00 UTC000
Sep 132013-09-13 00:00:00 UTC2013-09-14 00:00:00 UTC000
Sep 142013-09-14 00:00:00 UTC2013-09-15 00:00:00 UTC000
Sep 152013-09-15 00:00:00 UTC2013-09-16 00:00:00 UTC000
Sep 162013-09-16 00:00:00 UTC2013-09-17 00:00:00 UTC000
Sep 172013-09-17 00:00:00 UTC2013-09-18 00:00:00 UTC000
Sep 182013-09-18 00:00:00 UTC2013-09-19 00:00:00 UTC101

What Hacker News says

2 sources
It would be good to get Firebase's Angular bindings to work decently well for top-level objects and improve their promise support. I recently worked on http://worldmap.io as a way to test a bunch of angular-related tech and the firebase bindings, while dead easy to start, were a pain as I couldn't resolve them in the routeProvider. Instead I had to do it inside the controller, which forced me to keep a bunch of boilerplate. See https://github.com/alexandrosm/worldmap/blob/master/app/scri... Still, a great project and concept, just has some more way to go before I'd use it in a real project. I do want to check out https://github.com/marknutter/firebase-resource though, made by a fellow HNer and mentioned last time around.
In Angular + Firebase Is RAD
I've been using Firebase in an Angular app I've been developing for the past couple of months, but instead of using AngularFire I rolled my own wrapper for a few reasons: 1. I didn't like how Firebase is explicitly injected into and referred to in the controllers. I don't want my controllers to be so tightly coupled to Firebase. 2. There was no support for associations. If you want to have object associations, which most non-trivial apps require, you need to manage all that complexity in your controllers using AngularFire. I wanted a solution that handled it implicitly, ala ActiveRecord. 3. I wanted additional features handled for me by the wrapper like timestamps, save/create/delete/init callbacks, collecting resources into stores to be used across controllers, etc. 4. AngularFire leans pretty heavily on Firebase as the place data is sto
Read the rest
red. I wanted to instead have my data stored in memory and automatically synced to Firebase without me having to worry about it. That way, if I ever switched away from Firebase I don't need to change any of my controller code. 5. Pagination is something that becomes very important as you start to build more complex apps, and it's not the most pleasant thing to deal with in Firebase at present. I wanted a wrapper that managed all those details for me. Angular and Firebase are a great match, and AngularFire is a good way to get going quickly, but it lacks the features and depth required to make a truly complex application IMO. I had been meaning to throw my wrapper up on Github for a while so I suppose now is as good a time as any: https://github.com/marknutter/firebase-resource Examples and tests forthcoming.
In AngularFire - A real-time backend for AngularJS from Firebase

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.