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

loopback-connector-blazestore

v1.0.1

Published

Firestore connector for the LoopBack framework.

Downloads

9

Readme

loopback-connector-blazestore

Firestore connector for the LoopBack framework.

npm npm npm

Installation

Create a new database

Then you should use a service account. Go to Project Settings > Service Accounts in the Google Cloud Platform Console. Generate a new private key and save the JSON file.

You should fill the application's datasource file which is located in /server/datasources.json with those details, You can find them in the downloaded JSON file from the Google Cloud Platform.

"firestore": {
  "name": "<the_name_of_your_database>",
  "connector": "loopback-connector-blazestore",
  "projectId": "",
  "clientEmail":  "",
  "privateKey": "",
  "databaseName": "" // Optional, Default: projectId
}

Connection properties

| Property | Type   | Description | --- | | --- | --- | --- | --- | | projectId | String | project_id in the JSON file | --- | | clientEmail | String | client_email in the JSON file | --- | | privateKey | String | private_key in the JSON file | --- | | databaseName | String | Firebase's project id | Optional, Default: projectId | --- |

And you can actually store those private details as an Environment variables, Check source-configuration

License

Copylefted (c) 2017 Rodrigo Gonzalez Godoy Licensed under the MIT license.