npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

active-firestore

v1.2.2

Published

Firestore sdk which has ActiveRecord like syntax

Downloads

16

Readme

active-firestore

CI codecov

Firestore sdk which has ActiveRecord like syntax

Features

  • 🚀 No dependencies
  • ⚡️ Lightweight
  • ✏️ Less code
  • 💪 Type strong(Written in TypeScript)
  • 🔧 Customizable(You can add any methods you want)
  • 📚 Usable in nested collections
  • 🕒 Convert firestore.Timestamp to Date automatically

Usage

1. Install this npm package:

yarn add active-firestore
# or npm intall active-firestore

2. Initialize your Firebase SDK

/* src/plugins/firestore.ts */
import firebase from 'firebase/app'
import 'firebase/firestore'

// TODO: Replace the following with your app's Firebase project configuration
const firebaseConfig = {
  // ...
};

if (firebase.apps.length === 0) firebase.initializeApp(firebaseConfig)
export const db = firebase.firestore() 

NOTE: if you use firebase-admin, you should install a firebase package and initialize as below

import admin from "firebase-admin";
import { firestore } from 'firebase/app' // for type assertion

if (admin.apps.length === 0) admin.initializeApp();
const db = (admin.firestore() as unknown) as firestore.Firestore;

3. Add Application model to your project.

/* src/models/Application.ts */
import { Base, BaseObject } from 'active-firestore'
import { db } from '../plugins/firebase'

export class Application<T extends BaseObject> extends Base<T> {
  get baseProps(): typeof Base.prototype.props {
    return { db }
  }
}

4. Set model files depending on your firestore design.

For example,

  • root collection: users
    • name: string
    • child collection: posts
      • title: string
      • body: string
/* src/models/User.ts */
import { Application } from './Application'

type TUser = {
  name: string
}

export class User extends Application<TUser> {
  get props(): typeof Application.prototype.props {
    return {
      collectionName: 'users',
    }
  }
}
/* src/models/Post.ts */
import { Application } from './Application'
import { User } from './User'

type TPost = {
  title: string
  body: string
}

export class Post extends Application<TPost> {
  get props(): typeof Application.prototype.props {
    return {
      collectionName: 'posts',
      parent: User, // Set parent model
    }
  }
}

5. 🎉 Let's get data with simple API.

/* src/index.ts */
import { User } from '../models/User'
import { Post } from '../models/Post'

const userId = 'USER_ID'
const userDAO = new User(userId)
// Create
await userDAO.create({ name: 'user1' }) // or await new User().create({ name: 'user1' })
// Create with ID
await userDAO.create({ name: 'user1', id: 'USER_1' }) // firestore documentID will be `USER_1`
// Read
const userData = await userDAO.find()
// Read all
const usersData = await userDAO.all() // or await new User().all()
// Read all (limit 10)
const usersDataWithLimit = await userDAO.all({ limit: 10 }) // or await new User().all({ limit: 10 })
// Update
await userDAO.update({ name: 'user1-renamed' })
// Delete
await userDAO.destroy()

const postId = 'POST_ID'
const postDAO = new Post([userId], postId) // Path parent documentID in array
// Create
await postDAO.create({ title: 'title1', body: 'body1' }) // or await new Post([userId]).create({ title: 'title1', body: 'body1' })
// Read
const postData = await postDAO.find()
// Update
await postDAO.update({ title: 'title1-changed', body: 'body1-changed' })
// Delete
await postDAO.destroy()

// More nested (Comment is Post's child)
const commentDAO = new Comment([userId, postId], commentId)

Q. Why not syntax such as Post.find

A. Bacause Firestore is not RDB.

In Firestore, when you get data from post collection(example given above), you need not only postId but also userId(parent documentID). So:

Post.create(userId, { title: 'title1' }) // It's confusing! You use Post but API require `userId`
Post.find(userId, postId) // Not bad...?
Post.update(userId, postId, { title: 'title-changed' }) // It's confusing!
Post.destroy(userId, postId) // It's confusing!