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 🙏

© 2025 – Pkg Stats / Ryan Hefner

fireborm

v0.3.2

Published

A Firebase ORM-like wrapper, inspired by packages like sequelize and mongoose

Readme

FireBorm

A Firebase ORM-like wrapper, inspired by packages like sequelize and mongoose.

Why?

Using the firebase sdk to fetch data from Firestore and transform it to the model we use on the apps can sometimes be verbose.

This package solves this issue using an approach inspired in sequelize or mongoose.

Usage

Initializing fireborm also handles the firebase initialization, as well as emulators initialization.

// ./index.ts

import { FireBorm } from 'fireborm'

// Firebase config file
import { firebaseConfig } from '../../firebase-config'

// Initialize Fireborm singleton
const fireborm = new Fireborm(config, settings)

Stores

Stores correspond to Collections. The store class provides end-to-end type hinting without much hassle.

Declare a store by calling fireborm.createStore() and providing the arguments.

// ./store.ts

export const MyStore = fireborm.createStore<
	DocumentSchema, // Shape of the document in Firebase
	ModelSchema, // Shape of the transformed document, used in the app
	CreationSchema, // Shape of the minimum required data for creation
	DefaultSchema // Shape of the default object data
>({
	path: 'path-without-spaces',
	plural: 'Plural name',
	singular: 'Singular name',
	defaultData: {
		// as DefaultSchema, or DocumentSchema if omited
		id: crypto.randomUUID(),
		name: '',
		createdAt: new Date()
	},
	toModel: document => ({
		// Transforms DocumentSchema to ModelSchema
		...document.data(),
		id: document.id
	}),
	toDocument: ({ id, ...model }) => {
		// Transforms ModelSchema to DocumentSchema
		return model
	}
})

Then use the store in any file like:

// ./component.tsx

store.count({ onChange: count => setCount(count) })

useEffect(() => {
	store.subscribeMany({ onChange: res => setData(res) })
}, [store, getQuery])

Storages

Each Storage corresponds to a collection.

You declare each storage by calling fireborm.initializeStorage() and providing the arguments.

More information about the arguments, and the class returned will be added soon.