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

@gigster/module-loopback-firebase-authentication

v1.1.12

Published

Role | Name | Email | Slack ---- | ---- | ----- | ----- *Developer* | Name | [[email protected]](mailto:[email protected]) | [@fridiculous]

Downloads

52

Readme

Loopback Firebase Authentication

Role | Name | Email | Slack ---- | ---- | ----- | ----- Developer | Name | [email protected] | [@fridiculous]

Overview

This module enables a Firebase SDK with a loopback backend. By using this module, the api returns a firebaseAccessToken with when a user signs in via user/login endpoint. This token can then be used to sign into firebase from a client application.

See (using custom auth with Firebase docs)[https://firebase.google.com/docs/auth/web/custom-auth]

Usage

In your gig.yaml please update your modules as such:

  modules:
    - name: loopback-models
      location: >-
        https://github.com/liquidlabs-co/gig-modules/tree/master/block/loopback-models
      spec: {}
    - name: loopback-authentication
      location: >-
        https://github.com/liquidlabs-co/gig-modules/tree/master/block/loopback-authentication
      spec:
        webEnabled: true
        providers:
          local: {}
    - name: loopback-firebase-authentication
      location: >-
      'https://github.com/liquidlabs-co/gig-modules/tree/master/block/loopback-firebase-authentication'
      spec: {}

There is no specification for this module.

Dependencies

This is dependant on the loopback framework and these two other modules

  • loopback-models
  • loopback-authentication

Environment Variables

Make a shell script to export your environment variables.

export FIREBASE_PROJECT=
export FIREBASE_PROJECT_KEY_ID=
export FIREBASE_PRIVATE_KEY="-----BEGIN PRIVATE KEY-----\n  -----END PRIVATE KEY-----\n"
export FIREBASE_CLIENT_EMAIL=
export FIREBASE_CLIENT_ID=
export FIREBASE_CLIENT_X509_CERT_URL=

To get your environment variables for the firebase SDK, follow the instructions at the firebase admin docs

Generation

To generate this playground, try the following command

gig generate --path ../gig-modules/block/loopback-firebase-authentication/playground --verbose

Models

The module contributes the following models to the project.

Model | Attribute | Description ---- | ---- | ---- accessToken | firebaseAccessToken | the firebase access token used to authenticate with the firebase backend for a given user

Troubleshooting

To troubleshoot this, try to login via the api and see if a firebaseAccessToken is returned along with the user.

Tests

Module tests are defined using a test/scenarios.yaml file. This file defines the set of example gigs that we generate as part of integration testing. To run all tests, run yarn test at the root of this module.

Each scenario is generated in test/scenario/<name> which you can then cd into and run the actual app. For a scenario called default, this is done via:

cd test/scenario/default
yarn install

# Run tests.
yarn test

# Start the app.
yarn start

TODO