One feature people might find interesting is the “Collection Health Scan”.
Firestore has a number of limits that are easy to hit accidentally as a project grows (document size, number of fields, nesting depth, index entry limits, etc.). LazyFire can scan collections and highlight documents that approach or exceed those limits.
I originally built this because debugging Firestore issues in the Firebase Console was slow when working with large collections.
LazyFire also supports:
• browsing collections and documents
• running queries
• jq filtering of results
• vim-style keyboard navigation
• viewing Cloud Function logs
If anyone here is using Firestore at scale, I’d be curious:
- what’s the most annoying thing about the Firebase Console?
- are there features missing that would make a terminal tool useful?
Creator here
One feature people might find interesting is the “Collection Health Scan”.
Firestore has a number of limits that are easy to hit accidentally as a project grows (document size, number of fields, nesting depth, index entry limits, etc.). LazyFire can scan collections and highlight documents that approach or exceed those limits.
I originally built this because debugging Firestore issues in the Firebase Console was slow when working with large collections.
LazyFire also supports: • browsing collections and documents • running queries • jq filtering of results • vim-style keyboard navigation • viewing Cloud Function logs
If anyone here is using Firestore at scale, I’d be curious: - what’s the most annoying thing about the Firebase Console? - are there features missing that would make a terminal tool useful?