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

angular-springfire

v0.0.22

Published

A set of classes to help remove some boilerplate when dealing with CRUD operations using angularfire2.

Downloads

2

Readme

angular-springfire

A set of classes to help remove some boilerplate when dealing with CRUD operations using angularfire2.

I know that this probably isn't very good code, but I thought no harm in putting it out there.

The idea for this project came from trying to install Firestorm and not being able to get anything working due to it being so out of date. As a result I started this project to fill the gap I was trying to plug.

Professionally I work as a Java developer, so I just started implementing things how I would when working in that environment (this is where the name came from, referencing the spring framework).

The idea is to abstract away all common Firestore interactions so that your app contains less code while also making a lot of your database interactions consistent with one another. Another thing I want to ensure is that the ONLY dependency will be AngularFire, this should hopefully make sure that this project doesn't meet the same fate as Firestorm.

I honestly have no idea what I'm doing with this, and I'm only implementing features or changing things as the requirements for my current project change. Contributions are welcome, but ideally I would like to limit the code to things I can personally wrap my head around 😅. I think it would be cool and make sense for a lot of what's here to be converted into annotations, but I have no clue how to go about making those myself.